[release-1.12 CP] Issue #6728: support JSON Merge Patch and Strategic Merge Patch in Resource Modifiers

[27149chen]

cherry-pick #6917 to release 1.12: support JSON Merge Patch and Strategic Merge Patch in Resource Modifiers

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

Attention: 78 lines in your changes are missing coverage. Please review.

Comparison is base (3325a0c) 60.64% compared to head (5c44ed4) 60.61%.

Files	Patch %	Lines
...nternal/resourcemodifiers/strategic_merge_patch.go	36.61%	38 Missing and 7 partials ⚠️
internal/resourcemodifiers/resource_modifiers.go	75.47%	7 Missing and 6 partials ⚠️
internal/resourcemodifiers/json_patch.go	81.48%	7 Missing and 3 partials ⚠️
internal/resourcemodifiers/json_merge_patch.go	55.00%	6 Missing and 3 partials ⚠️
pkg/restore/restore.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           release-1.12    #7049      +/-   ##
================================================
- Coverage         60.64%   60.61%   -0.03%     
================================================
  Files               247      250       +3     
  Lines             26527    26683     +156     
================================================
+ Hits              16087    16175      +88     
- Misses             9314     9367      +53     
- Partials           1126     1141      +15     

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

[anshulahuja98]

@27149chen I am not sure if we should take a big change now to 1.12
I don't think this was in initial plan to pull to 1.12

[ywk253100]

@27149chen You need to rebase the commit to resolve This branch is out-of-date with the base branch warning

[anshulahuja98]

1 small nitpick - we missed making the PR title reflect the cherry picked feature.

[27149chen]

@anshulahuja98 what's the correct title for cherry-pick prs?

[anshulahuja98]

PR title guidelines: https://github.com/sseago/velero/blob/cd7e2d6fcc515c11098d85ef933b2089fb6e0770/site/content/docs/main/code-standards.md?plain=1#L11

[anshulahuja98]

Should have ideally included the original PR naming
something to indicate what this PR is for apart from the Issue number