Add Backup warning for inclusion of NS managed by ArgoCD

[shubham-pampattiwar]

Thank you for contributing to Velero!

Please add a summary of your change

This change adds a warning to velero backup operation if there are namespaces included in the backup which are managed by ArgoCD.

We’ve observed conflicts between Velero and ArgoCD in such environments and produce undesirable outcomes. This backup warning serves as a notification to ensure users are aware of the potential problems.

Does your change fix a particular issue?

Fix Related to #7905

Please indicate you've done the following:

• Accepted the DCO. Commits without the DCO will delay acceptance.
• Created a changelog file (make new-changelog) or comment /kind changelog-not-required on this PR.
• Updated the corresponding documentation in site/content/docs/main.

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 9 lines in your changes missing coverage. Please review.

Project coverage is 58.96%. Comparing base (42de654) to head (738bb79).
Report is 100 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/backup/backup.go	66.66%	8 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8257      +/-   ##
==========================================
- Coverage   59.21%   58.96%   -0.25%     
==========================================
  Files         367      368       +1     
  Lines       30841    39000    +8159     
==========================================
+ Hits        18262    22996    +4734     
- Misses      11119    14539    +3420     
- Partials     1460     1465       +5     

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[mateusoliveira43]

Should we check if label exist here instead of checking if its value is not an empty string?

[kaovilai]

That would probably be better.. as long as we know it is possible label only need key and empty value is ok

[shubham-pampattiwar]

The rationale here is the having an empty value for the ArgoCD label key would not make much sense, so this acts as a additional check.

[kaovilai]

While it may not make sense, we need to match whatever argocd logic is regarding namespace it manages. If it disallows empty value label then current code is fine.

[kaovilai]

Looks like the value here should never be empty according to docs. Value would be namespace where argocd instance lives. An Argo CD instance always live in a namespace, and namespaces are never empty string.

We can just check if length is > 0 in this case.

[reasonerjt]

lgtm