Store CA configuration as secret

[jmcshane]

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