Add DataUpload Result and CSI VolumeSnapshot check for restore PV.

[blackpiglet]

Thank you for contributing to Velero!

Please add a summary of your change

Does your change fix a particular issue?

Fixes #(issue)

Please indicate you've done the following:

• Accepted the DCO. Commits without the DCO will delay acceptance.
• Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
• Updated the corresponding documentation in site/content/docs/main.

[codecov]

Codecov Report

Merging #7061 (1fb0529) into main (a221a88) will increase coverage by 0.03%.
Report is 34 commits behind head on main.
The diff coverage is 65.20%.

@@            Coverage Diff             @@
##             main    #7061      +/-   ##
==========================================
+ Coverage   61.01%   61.04%   +0.03%     
==========================================
  Files         255      255              
  Lines       27050    27119      +69     
==========================================
+ Hits        16504    16556      +52     
- Misses       9364     9382      +18     
+ Partials     1182     1181       -1     

Files	Coverage Δ
.../resourcemodifiers/resource_modifiers_validator.go	100.00% <100.00%> (ø)
pkg/exposer/csi_snapshot.go	90.88% <100.00%> (ø)
pkg/restore/request.go	100.00% <ø> (ø)
pkg/repository/config/aws.go	50.00% <50.00%> (ø)
pkg/controller/restore_controller.go	65.84% <40.00%> (-0.25%)	⬇️
pkg/repository/provider/unified_repo.go	86.05% <25.00%> (ø)
internal/resourcemodifiers/json_merge_patch.go	55.00% <55.00%> (ø)
internal/resourcemodifiers/json_patch.go	81.48% <81.48%> (ø)
internal/resourcemodifiers/resource_modifiers.go	71.92% <75.47%> (ø)
pkg/restore/restore.go	66.08% <71.08%> (+0.32%)	⬆️
... and 1 more

... and 5 files with indirect coverage changes

[anshulahuja98]

@blackpiglet is this PR for resolving the issue discussed in #6595
If yes, do you want to take it as different PR/commit which can be cherry picked to previous releases?

[blackpiglet]

@blackpiglet is this PR for resolving the issue discussed in #6595 If yes, do you want to take it as different PR/commit which can be cherry picked to previous releases?

@anshulahuja98
Yes, this PR is used to add the backward-compatible fix for the previous releases.
Sure, after this PR is merged, I will create cherry-pick PRs for older releases.

[Lyndon-Li]

@blackpiglet Shouldn't the implementation use the backup volume info in design #6962?

[blackpiglet]

@blackpiglet Shouldn't the implementation use the backup volume info in design #6962?

The reason this change is also needed for the main release is that the main Velero release also needs to handle the backup generated by the old Velero.
The old version backup doesn't have the VolumeInfo metadata.
The main Velero needs to have this PR as a fall-back.

[shubham-pampattiwar]

@blackpiglet So for the implementation PR of the design #6962, you will be updating the switch case function here to check for VolumeInfo and use that struct/file/data if present or else fall back on the current PR's code, Is this the plan ?
Also, the CP would be clean and easy to backup-port to earlier releases. ++ @blackpiglet

[blackpiglet]

@blackpiglet So for the implementation PR of the design #6962, you will be updating the switch case function here to check for VolumeInfo and use that struct/file/data if present or else fall back on the current PR's code, Is this the plan ? Also, the CP would be clean and easy to backup-port to earlier releases. ++ @blackpiglet

@shubham-pampattiwar
Exactly. The cherry-pick will only contain this PR's content.