1. Proposed title of this feature request
Defining webhook secrets in a declarative way

2. What is the nature and description of the request?
Today webhook secrets can only be managed by editing the operator managed secret "argocd-secret" directly according to this documentation
We would like to provide and manage webhook secrets in a declarative way just like we make additions to the argocd-cm via "extraConfig" or by providing ssh keys for repositories, etc. as a similar example in the argocd manifest

3. Why does the customer need this? (List the business requirements here)
Directly changing operator managed resources is problematic in multiple ways.
Addititonal reasons are the same as https://github.com/argoproj/argo-cd/issues/8154

4. How would the customer like to achieve this? (List the functional requirements here)
Ideally as part of the argocd manifest, similar to how additions to the argocd-cm via "extraConfigs" can be managed:
https://argocd-operator.readthedocs.io/en/latest/usage/extra-config/

5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Adding the webhook secret in the argocd manifest results in the webhook secret being part of the argocd-secret.
Push requests from a repository to argocd are only being accepted by providing the correct secret.