As a cluster admin, I would like to provide some bundle configuration parameters in a Secret (e.g. passwords, api keys, token, etc.) in order to not expose them on the ClusterExtension's API surface and thereby ensure the security of my cluster and its resources.

Open Question:

• which service account reads the secret? The CE's? OLM's?

A/C:

 - Add support for referencing Secrets in the ClusterExtention's .spec.Config API
 - Its ok if the ClusterExtension configuration only accepts only one of inline or secret ref configuration

 - Unit tests
 - e2e test