Add design to introduce restore volume info

[reasonerjt]

• 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

All modified and coverable lines are covered by tests ✅

Project coverage is 61.86%. Comparing base (13f4efd) to head (ab5ee7b).
Report is 55 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7610      +/-   ##
==========================================
+ Coverage   61.68%   61.86%   +0.18%     
==========================================
  Files         263      266       +3     
  Lines       28826    29456     +630     
==========================================
+ Hits        17781    18224     +443     
- Misses       9787     9941     +154     
- Partials     1258     1291      +33     

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

[blackpiglet]

Could you explain more on why the mutex is needed here?
Didn't find where it is used.

[reasonerjt]

It's introduced to make tracker thread-safe, considering velero may improve parallelism to handle multiple resources in one restore in future.
An example of usage:

func (t *RestoreVolumeInfoTracker) TrackNativeSnapshot(pvName string, snapshotHandle, volumeType, volumeAZ string, iops int64) {
	t.Lock()
	defer t.Unlock()
	t.pvNativeSnapshotMap[pvName] = NativeSnapshotInfo{
		SnapshotHandle: snapshotHandle,
		VolumeType:     volumeType,
		VolumeAZ:       volumeAZ,
		IOPS:           strconv.FormatInt(iops, 10),
	}
}