WHY
Changing quota should not cause any issues.

WHAT
If quota change is not finished successfully changing the quota back might not help to recover. Example: you have small cluster using 100k quota. Then you change to 100M quota. This failes because you cluster just doesn't have enough resources to accommodate all the new required Pods. So you change it back to 100k. However, RHOAM (3cale) just don't recover in this scenario. Workaround seems to be to manually change APIManager CR to trigger the reconciliation. Restarting operator Pod does not help

HOW
?

TESTS
N/A

DONE
Quota changing is more robust
Scenario described above works as expected