Bugfix argocd_manage_add_ons not passed to external_secrets module

[atorrescogollo]

What does this PR do?

When enabling external_secrets addon, it will deploy the helm chart regardless of what you configured through argocd_manage_add_ons. It should instead create only AWS IAM stuff and the namespace with the service account.

Motivation

• Resolves External secrets will install helm chart regardless of argocd_manage_add_ons configuration #956

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]

Thanks for the PR!

[jochemvankessel]

I think you forgot to add a line to /main/modules/kubernetes-addons/locals.tf
The gitops config is not added there