[HOLD] Throw error if reverse-sync needed, but not allowed

[AlanCoding]

This is a re-do of #618 that attempts to answer the question "what if someone runs awx-manage createsuperuser manually?"

If that command is ran with explicit disabling of reverse-sync, then it will be allowed. It will be confusing that doing this is still permitted even through local_resource_management is off.

But what's the most wrong is to have

• ALLOW_LOCAL_RESOURCE_MANAGEMENT False
• reverse sync enabled (multiple mechanisms involved)

The argument is that this configuration is so dangerously contradictory that we should throw an error so that we can front-load debugging of the situation.

[relrod]

Comments:

• Sonar can be ignored here, we use Exception above this anyway.
• I like this approach better than [Alt 1] Flip default of reverse sync to True #618, this has my vote.
• Can we add a quick unit test for this in test_app/tests/resource_registry/test_utils.py

Beyond that, this LGTM.

[AlanCoding]

I identified a conflict with awx-operator, and probably more. This would probably break things, and our viable path forward may be to go back to Alt 1 out of necessity.

[sonarcloud]

Quality Gate failed

Failed conditions
50.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud