Description of problem:

After enabling  ROBOTS_DISALLOW, the existing robot account which be created before enabling ROBOTS_DISALLOW can still be updated  in UI. 

Version-Release number of selected component (if applicable):

quay-operator-bundle-container-v3.10.0-118
------------------------------
$ oc get $(oc get pod -l name=quay-operator-alm-owned -o name -n quay-enterprise) -o jsonpath='{.spec.containers[0].image}' -n quay-enterprise
registry.redhat.io/quay/quay-operator-rhel8@sha256:28ee8e59cb48bcf2b3592fcca97419810a1c790af09ddc5fd8a7e5b731938d33
------------------------------
$ oc get $(oc get pod -l app=quay -o NAME -n quay-enterprise|head -n 1) -o jsonpath='{.spec.containers[0].image}' -n quay-enterprise
registry.redhat.io/quay/quay-rhel8@sha256:b3cd20cc23b9d82cdc6f72e737829d5b8528d344635c2d3b3d7a7c6e4d82b683

How reproducible:

1. Do not set `ROBOTS_DISALLOW` in config bundle,  deploy quay as common
2. create a user, then create a organization and a repository "repo1"
3. create a robot account "superrobot" with "write" permission of "repo1" in UI

  4. set "ROBOTS_DISALLOW: true" in config bundle and reconcile the quay pods

  5.  update repository permission of robot account "superrobot" for "repo1" from "write" to "read" in UI

Actual results:

The repository permission is updated successfully.

Expected results:

Due to `ROBOTS_DISALLOW` has been disabled.  So when update repository permission in UI should get error message and the update operation should be unsuccessful.