Fix dynatrace workload installation (#9129)

* Removing the monitoring-dynatrace applicationset

We will continue to handle the dynatracing installation as part
of the workload monitoring component.

* Add dynatrace to cluster secret config to get access to appsre-stonesoup-vault

* Add annotation to avoid having sync option conflict

This will ensure the CRD and CR are installed in the right order

---------

Co-authored-by: rrajashe <[email protected]>

Author: raks-tt

argo-cd-apps/base/monitoring-dynatrace/kustomization.yaml

@@ -9,7 +9,6 @@ resources:
   - ../../base/eaas
   - ../../base/monitoring-blackbox
   - ../../base/monitoring-registry
-  - ../../base/monitoring-dynatrace
 
 namespace: konflux-public-staging
 patchesStrategicMerge:

argo-cd-apps/base/monitoring-dynatrace/monitoring-dynatrace.yaml

@@ -28,6 +28,7 @@ spec:
   conditions:
     - namespaces:
         - dora-metrics
+        - dynatrace
         - application-service
         - appstudio-workload-monitoring
         - group-sync-operator

argo-cd-apps/overlays/konflux-public-staging/kustomization.yaml

@@ -11,3 +11,6 @@ namespace: dynatrace
 generatorOptions:
   disableNameSuffixHash: true
 
+# https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#skip-dry-run-for-new-custom-resources-types
+commonAnnotations:
+  argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true