Bump up sidecars to k8s 1.30 releases

[chethanv28]

What this PR does / why we need it:
Bump up sidecars to latest versions that are recommended for k8s 1.30 release

New versions added by this PR:

snapshot-validation-webhook:v8.0.1
csi-attacher:v4.6.1
csi-resizer:v1.11.1
csi-snapshotter:v8.0.1
node-driver-registrar: 2.10.1
csi-provisioner:5.0.1

The PR disables the topology feature flag for provisioner, because the feature is now GA'ed and enabled by default in provisioner. However, for non topology deployments the flag has to be set to false to avoid the breaking changes to have any effect on volume provisioning.

Node driver registrar is not upgraded to latest (2.11.0) due to this issue: kubernetes-csi/node-driver-registrar#415

Release note:

Bump up sidecars to latest versions that are recommended for k8s 1.30 release

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chethanv28

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 [chethanv28]

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

[svcbot-qecnsdp]

Started Vanilla block pre-checkin pipeline... Build Number: 2814

[svcbot-qecnsdp]

Started Vanilla block pre-checkin pipeline... Build Number: 2820

[svcbot-qecnsdp]

Build ID: 2820
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 1 of 857 Specs in 379.095 seconds
FAIL! - Interrupted by User -- 0 Passed | 1 Failed | 0 Pending | 856 Skipped
--- FAIL: TestE2E (379.16s)
FAIL

Ginkgo ran 1 suite in 7m20.807684589s

Test Suite Failed

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 2611

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 1 of 857 Specs in 910.705 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 856 Skipped
--- FAIL: TestE2E (910.76s)
FAIL

Ginkgo ran 1 suite in 16m12.069783441s

Test Suite Failed

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 857

[svcbot-qecnsdp]

Build ID: 857
File vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 870 Skipped
--- FAIL: TestE2E (304.09s)
FAIL

Ginkgo ran 1 suite in 5m56.169842064s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/csi-file-vanilla-precheckin/857/vsphere-csi-driver`

[svcbot-qecnsdp]

Started Vanilla file pre-checkin pipeline... Build Number: 858

[svcbot-qecnsdp]

Build ID: 858
File vanilla build status: SUCCESS 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 

Ran 1 of 871 Specs in 302.614 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 870 Skipped
PASS

Ginkgo ran 1 suite in 5m57.13076748s
Test Suite Passed
make: Leaving directory `/home/worker/workspace/csi-file-vanilla-precheckin/858/vsphere-csi-driver`

[svcbot-qecnsdp]

Started Vanilla block pre-checkin pipeline... Build Number: 2826

[svcbot-qecnsdp]

Build ID: 2826
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 871 Specs in 415.521 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 870 Skipped
PASS

Ginkgo ran 1 suite in 8m4.748267623s
Test Suite Passed
--
Ran 2 of 871 Specs in 2164.396 seconds
FAIL! -- 0 Passed | 2 Failed | 0 Pending | 869 Skipped
--- FAIL: TestE2E (2164.47s)
FAIL

Ginkgo ran 1 suite in 36m22.80356162s

Test Suite Failed

[svcbot-qecnsdp]

Started Vanilla block pre-checkin pipeline... Build Number: 2844

[svcbot-qecnsdp]

Build ID: 2844
Block vanilla build status: SUCCESS 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 0 of 877 Specs in 0.014 seconds
SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 877 Skipped
PASS

Ginkgo ran 1 suite in 1m7.492217346s
Test Suite Passed

[divyenpatel]

/hold

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale