Remove check for pods to be on unique nodes, reduce num files in vdbench

[Rohit-PX]

Signed-off-by: Rohit-PX [email protected]

What type of PR is this?
integration-test

What this PR does / why we need it:
Stork does not guarantee pods to be deployed on different nodes all the time. So this check is not valid.

Does this PR change a user-facing CRD or CLI?:
No.

Is a release note needed?:
No.

Does this change need to be cherry-picked to a release branch?:
master

[Rohit-PX]

Tested code changes:

--- PASS: TestExtender (1392.41s)
    --- PASS: TestExtender/pvcOwnershipTest (357.70s)
    --- PASS: TestExtender/noPVCTest (60.19s)
    --- PASS: TestExtender/singlePVCTest (130.38s)
    --- PASS: TestExtender/statefulsetTest (120.31s)
    --- PASS: TestExtender/multiplePVCTest (90.24s)
    --- PASS: TestExtender/driverNodeErrorTest (633.58s)
PASS

DONE 7 tests in 1408.362s

[Rohit-PX]

Job ran successfully here:
https://jenkins.portworx.dev/job/Stork/view/Stork%202.7/job/storkstork-2.7-px-2.9-dev-csi-backup/3/

[cnbu-jenkins]

Can one of the admins verify this patch?