Feat/dataprotection clustergroup

[eastaga]

1. What this PR does / why we need it:
   CG Data Protection and Backup Schedule

2. Which issue(s) this PR fixes

    (optional, in `fixes #<issue number>` format, will close the issue(s) when PR gets merged):
   
    Fixes #
   

3. Additional information

4. Special notes for your reviewer

[vmwclabot]

@eastaga, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 701336a has a no-reply/unreachable author email address: 53172692+rnarenpujari@users.noreply.github.com
• Commit 9600c9c has a no-reply/unreachable author email address: 49699333+dependabot[bot]@users.noreply.github.com
• Commit d2a42b7 has a no-reply/unreachable author email address: 45195720+eastaga@users.noreply.github.com

[vmwclabot]

@eastaga, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 701336a has a no-reply/unreachable author email address: 53172692+rnarenpujari@users.noreply.github.com
• Commit 9600c9c has a no-reply/unreachable author email address: 49699333+dependabot[bot]@users.noreply.github.com
• Commit d2a42b7 has a no-reply/unreachable author email address: 45195720+eastaga@users.noreply.github.com
• Commit e0ee294 must be signed by asagarwal@vmware.com

[eastaga]

[rnarenpujari]

Just skimmed through since we already reviewed the individual MRs.
The commit history is a bit messed up - can we clean that up a bit or enable squashing when you merge?

[codecov-commenter]

Codecov Report

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

Comparison is base (88ddf24) 25.29% compared to head (312af6e) 25.40%.

Files	Patch %	Lines
internal/resources/backupschedule/scope/scope.go	0.00%	28 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #375      +/-   ##
==========================================
+ Coverage   25.29%   25.40%   +0.10%     
==========================================
  Files         192      195       +3     
  Lines       16722    16784      +62     
==========================================
+ Hits         4230     4264      +34     
- Misses      12274    12302      +28     
  Partials      218      218              

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

[ramya-bangera]

Just glanced through the PR assuming it is end to end validated in the feature branch before seeking merge to main.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.