fix: Argo and Keda TF plan repeated changes gitops example

[Zvikan]

What does this PR do?

• Removes secret manager data source from argo example
• Changes set sensitive to use random password instead of secret manager data source
• Explicit set keda to not create SA via helm in the argo example

🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

• Resolves [BUG] fix argocd module idempotency #1113
• Resolves Repeated non-changes #1098
• Resolves issues where keda plan in the argo example will keep updates required of removing labels from the service account (IRSA) that was created by Terraform, the labels were added by helm because there was no explicit call to disable creating and manage the SA by helm.

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs require a new example and/or doc page. In general:

• Use an existing example when possible to demonstrate a new addons usage
• A new docs page under docs/add-ons/* is required for new a new addon

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

[askulkarni2]

Why set_sensitive?

[Zvikan]

fixed to values! thanks