feat: Add VolumeID to Mount request

[micahhausler]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds the VolumeID to the request so providers can make smarter caching decisions once requiresRepublish is implemented.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #1754

Special notes for your reviewer:

I opted to name the key with the DNS namespace for this project as there isn't a corresponding CSI key I could find in the Kubernetes codebase (the volume ID is just an attribute of the request, not an encoded key). Let me know if there is a better key name to use

TODOs:

• squashed commits
• includes documentation
• adds unit tests

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.61%. Comparing base (87f51ec) to head (3449397).
Report is 131 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1755      +/-   ##
==========================================
+ Coverage   35.83%   36.61%   +0.77%     
==========================================
  Files          63       63              
  Lines        3759     4534     +775     
==========================================
+ Hits         1347     1660     +313     
- Misses       2268     2731     +463     
+ Partials      144      143       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[benjaminapetersen]

Seems reasonable to me.
@aramase or @enj for 👀.

[enj]

/assign aramase

Rationale in linked issue seems reasonable but will defer to Anish since he is more familiar with CSI.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: micahhausler
Once this PR has been reviewed and has the lgtm label, please ask for approval from aramase. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[micahhausler]

/retry

[k8s-ci-robot]

@micahhausler: The following tests 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-secrets-store-csi-driver-e2e-provider-k8s-1-29-4	5428978	link	true	/test pull-secrets-store-csi-driver-e2e-provider-k8s-1-29-4
pull-secrets-store-csi-driver-e2e-provider-k8s-1-30-2	5428978	link	true	/test pull-secrets-store-csi-driver-e2e-provider-k8s-1-30-2
pull-secrets-store-csi-driver-e2e-provider-k8s-1-28-9	5428978	link	true	/test pull-secrets-store-csi-driver-e2e-provider-k8s-1-28-9
pull-secrets-store-csi-driver-e2e-windows	3449397	link	true	/test pull-secrets-store-csi-driver-e2e-windows

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.

[aramase]

The changes look fine!

This can only be merged after we support RequiresRepublish because the rotation controller doesn't have access to the volumeID.

/hold

token could differ between volume mounts (ex: pod1/mount1 uses token1 for credentials in cloud region us-east-1, pod1/mount2 uses the same token1 for credentials in cloud region us-west-2. The AWS provider allows such a configuration)

Isn't it easier for the provider to use the region in this case or other provider specific information another dimension of cache key? The pod uid will be the first dimension.

[aramase]

/retitle feat: Add VolumeID to Mount request