Store CA configuration as secret

Access to the CA configuration allows users to see the usernames and passwords of all identities within the CA, specifically the bootstrap admin identity. While it is necessary to store the secret data for things like the peer within the ibppeer CRD itself, storing secret data in a configmap reduces the ability to create a "read" type configuration on a cluster where this operator is deployed.

Could this be a configurable aspect of the operator? the CM is already set to binaryData, so it could be easily modified to a secret

Locate the Go code that creates the CA ConfigMap and the ibppeer CRD handling; start by tracing how CA configuration is assembled and stored in binaryData. Define the configuration choice and verify that secret data is stored in a Secret when selected, while required peer data remains in the CRD.

Written by the indexing model from the issue text.