Story (Required)

Introduce a new label: operator.argoproj.io/tracked-by=argocd. This label will be applied to all secret and configmap resources managed or watched by the operator. Using this label, we can configure the controller-runtime cache to filter and store only relevant objects.

Refer to the implementation in this PR for argocd-operator.
We need to implement similar logic for Secrets and ConfigMaps created by the gitops-operator.
Some of these resources will already have the new label once we update the argocd-operator commit in go.mod.
We need to identify the remaining Secrets and ConfigMaps that are missing this label and update them accordingly.

Background and Approach (Required)

• Background: https://docs.google.com/document/d/1b-dTIwYo-E4wTM7MZRBx0likSVtlvk__ROMB1lT3P2k/edit?tab=t.0 

Acceptance Criteria (Mandatory)

• Operator adds operator.argoproj.io/watched-by=argocd on all configmaps and secrets it creates/manages.
• e2e/unit tests are added/updated.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.