(wip) fix flaky unit tests

[adikul30]

What this PR does / why we need it:

#3083 introduced a goroutine for restarting the container after a specified amount of time in case listview is not up and session is valid.

This PR prevents running this goroutine during unit tests as it's not required for unit tests and can cause some flakiness.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
A PR must be marked "[WIP]", if no test result is provided. A WIP PR won't be reviewed, nor merged.
The requester can determine a sufficient test, e.g. build for a cosmetic change, E2E test in a predeployed setup, etc.
For new features, new tests should be done, in addition to regression tests.
If jtest is used to trigger precheckin tests, paste the result after jtest completes and remove [WIP] in the PR subject.
The review cycle will start, only after "[WIP]" is removed from the PR subject.

Special notes for your reviewer:

Release note:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adikul30

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [adikul30]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[adikul30]

/ok-to-test

[adikul30]

/retest

[adikul30]

/retest pull-vsphere-csi-driver-unit-test

[k8s-ci-robot]

@adikul30: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test pull-vsphere-csi-driver-build
• /test pull-vsphere-csi-driver-unit-test
• /test pull-vsphere-csi-driver-verify-fmt
• /test pull-vsphere-csi-driver-verify-golangci-lint
• /test pull-vsphere-csi-driver-verify-markdown
• /test pull-vsphere-csi-driver-verify-shell
• /test pull-vsphere-csi-driver-verify-staticcheck
• /test pull-vsphere-csi-driver-verify-vet

Use /test all to run the following jobs that were automatically triggered:

• pull-vsphere-csi-driver-build
• pull-vsphere-csi-driver-unit-test
• pull-vsphere-csi-driver-verify-fmt
• pull-vsphere-csi-driver-verify-golangci-lint
• pull-vsphere-csi-driver-verify-staticcheck
• pull-vsphere-csi-driver-verify-vet

In response to this:

/retest pull-vsphere-csi-driver-unit-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[adikul30]

/test pull-vsphere-csi-driver-unit-test

[adikul30]

cc: @chethanv28

[adikul30]

/test pull-vsphere-csi-driver-unit-test

[adikul30]

/test pull-vsphere-csi-driver-unit-test

[k8s-ci-robot]

@adikul30: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-vsphere-csi-driver-unit-test	918f5c4	link	true	/test pull-vsphere-csi-driver-unit-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.