Validate application S3 profile names against hub configmap

[parikshithb]

Problem

When validate application runs on a hub shared by multiple managed clusters, the report shows S3 profile gather results but doesn't show which profiles actually belong to the application. Developers have to manually trace DRPC → DRPolicy → DRClusters or inspect the VRG to figure out which profiles are relevant.

After we fix the S3 profile filtering bug (gathering only the app's profiles from primary VRG spec.s3Profiles), we should expose that list in the report and validate consistency.

Proposed solution

Add the primary VRG's s3Profiles list to the report and validate that each name in the list exists in the hub configmap's s3StoreProfiles. Flag a problem if they don't match.

Alternatives considered

None

User experience

No new commands or flags. The report will show the expected profile names from the VRG and flag if any are missing from the hub configmap.

Configuration

No new configuration needed.

Documentation

Update example reports with the new info

Security and privacy

No change. S3 profile names are not sensitive.

Backward compatibility

Adds new validated fields to the report. No breaking changes.

Performance

No impact, simple string comparison.

Testing

• Test case where VRG profiles match configmap (ok).
• Test case where VRG references a profile not in configmap (problem).