OSUS added support for annotations on update-service pods which rolls out new update-service when the graph-data image sha is changed in https://github.com/openshift/cincinnati-operator/pull/164/files

this feature today supports just one by-tag UpdateService.

Although this does not stop users from deploying multiple UpdateService instances, only the 1st instance sha is added as annotation for all update service instances. 

This ticket adds support for multiple by-tag UpdateServices so a graph-data pod should be running for all instances of UpdateService.

Definition of Done: 

• each operator CR has its own graph-data pod which is used to keep a watch on SHA change.