Description of problem (please be detailed as possible and provide log
snippests):

Old operator's name "Cincinnati" was deprecated and new name should be "update-service"(or maybe updateservice) in other places. Just found one missing place in Subscription as following(the operator's name was still cincinnati-operator):

1. ./oc get sub -n openshift-update-service -ojson|jq .items[].spec
   {
   "channel": "v1",
   "installPlanApproval": "Automatic",
   "name": "cincinnati-operator",
   "source": "osus-cs",
   "sourceNamespace": "openshift-marketplace",
   "startingCSV": "update-service-operator.v4.6.0"
   }

I think it should because the OPERATOR_NAME in csv was still the old one.

1. ./oc get csv update-service-operator.v4.6.0 -oyaml|grep -A1 OPERATOR_NAME

• name: OPERATOR_NAME
  value: cincinnati-operator

Version of all relevant components (if applicable):
OSUS operator image: v4.6.0-6
Bundle image: v1.0-20
Operand image: v4.6.0-8

Can this issue reproducible?
always

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
1. Install osus operator successfully
2. Check the Subscription Details from web-console or command-line
3.

Actual results:
Operator's name was cincinnati-operator

Expected results:
Operator's name should comply with other places

Additional info:
About current operator's name, there are two other names "update-service-operator" and "updateservice-operator" now. It's better to unify them.

Such as the name of csv is "update-service-operator":

1. ./oc get csv update-service-operator.v4.6.0 -ojson|jq .metadata.name
   "update-service-operator.v4.6.0"
   But most of resources' name are "updateservice-operator"
2. ./oc get csv update-service-operator.v4.6.0 -oyaml|grep "updateservice-operator"|wc -l
   10