Description of the problem:

How reproducible:
If the orchestrator CR is in a Failed state, deleting the orchestrator CR hangs. The deployed operators (in this case, OSL and serverless) are deleted, but the orchestrator CR itself is not being deleted.

Steps to reproduce:

1. Deploy orchestrator operator 1.5.0

2. Create orchestrator CR that will fail (in case, with the rhdh operator installment disabled, see FLPATH-2315)

3. Orchestrator CR state is failed

4. Try deleting the orchestrator CR.

Actual results: 
Operators deployed by the orchestrator CR are deleted, but Orchestrator CR deletion itself hangs.

Expected results: Orchestrator CR deletion should not hang.
Orchestrator CR: orchestrator-orchestrator (1).yaml
Orchestrator operator controller pod logs: orchestrator-operator-controller-manager-68c7d6d66b-x5z9b-manager.log