Unit test TestNodeTopology/add-csi-node flakes

[jsafrane]

What happened:
The unit test "TestNodeTopology/add-csi-node" flakes a bit. See https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-csi_external-provisioner/1373/pull-kubernetes-csi-external-provisioner-unit/1920740602429837312 for report from our CI.

--- FAIL: TestNodeTopology (60.26s)
    --- FAIL: TestNodeTopology/add-csi-node (60.00s)
        nodes_test.go:551: unexpected error: get informers in sync: timed out waiting for the condition

How to reproduce it:
I reproduced it in v5.2.0:

$ # install `stress` tool
$ go install golang.org/x/tools/cmd/stress@latest

$ # Compile the unit tests
$ git checkout v5.2.0
$ cd pkg/capacity/topology
$ go test -c -race

$ stress -p 40 ./topology.test

(Where 40 is ~ 2x nr. of my CPUs to generate some load, the tests sleep a lot)

After few minutes:

3m10s: 6308 runs so far, 10 failures (0.16%), 40 active

[jsafrane]

/help
/good-first-issue

[k8s-ci-robot]

@jsafrane:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

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.

[darshansreenivas]

/assign