CLONE - Improve cbopcfg options in Operator 2.0

Request:

Improve `cbopcfg` options in Operator 2.0 for deploying the Operator and Admission Controller. It would be good to add an option with the below deployment commands to indicate what is being deployed.

Background:

The below command is used to deploy the `Admission Controller` in a custom namespace. Though the usage of the "-no" option is common there is no indication that the below command will be installing the `Admission Controller` since it just says `-no-operator`.

./cbopcfg --no-operator --namespace camelot | kubectl create -n camelot -f -

The same goes for deploying the Operator. The below command is used to deploy the `Operator` in a custom namespace. There is no indication that the below command will be installing the `Operator` since it just says `--no-admission`.

./cbopcfg --no-admission --namespace asgard | kubectl create -n asgard -f -