Bug 2082538: bump cluster-capi-operator apirequests upper bound for GCP and Azure
Bug 2082538: bump cluster-capi-operator apirequests upper bound for GCP
and Azure

When deploying OCP on GCP with enabled CAPI, we got this error
from the tests:

"Operator \"cluster-capi-operator\" produces more watch requests than expected: watchrequestcount=63, upperbound=38, ratio=1.6578947368421053"

On Azure it is

"Operator \"cluster-capi-operator\" produces more watch requests than expected: watchrequestcount=65, upperbound=62, ratio=1.0483870967741935",

Bumping the upperbound to 36 should solve this issue.

bparees/origin,mfojtik/origin,openshift/origin,deads2k/origin,hroyrh/origin,csrwng/origin,soltysh/origin,mfojtik/origin,mahak/origin,mahak/origin,openshift/origin,soltysh/origin,sallyom/origin,hroyrh/origin,jsafrane/origin,jsafrane/origin,jsafrane/origin,sallyom/origin,csrwng/origin,deads2k/origin,mahak/origin,akram/origin,mfojtik/origin,sallyom/origin,csrwng/origin,bparees/origin,akram/origin,bparees/origin,soltysh/origin,akram/origin,deads2k/origin,hroyrh/origin,openshift/origin