Description of the problem:
When installing the go-based operator 1.5.0 in a disconnected environment, if the orchestrator resource is created with spec.rhdh.installOperator set to false but the serverless and serverless-logic operators enabled, the OSL and Serverless operators are created but the orchestrator CR itself's status is failed:

status:
  conditions:
    - lastTransitionTime: '2025-05-06T12:25:27Z'
      message: Starting Reconciliation
      reason: Reconciling
      status: Unknown
      type: Available
    - lastTransitionTime: '2025-05-06T12:27:27Z'
      message: no matches for kind "Backstage" in version "rhdh.redhat.com/v1alpha3"
      reason: ReconcilingRHDHResourcesFailed
      status: 'False'
      type: Degrading
  phase: Failed 

There was no existing RHDH operator or resources in the environment.

How reproducible: 100%

Steps to reproduce:

1. See above.

Actual results:
Orchestrator CR status is failed, OSL and Serverless operators were installed correctly. The orchestrator operator is looking for the backstage resource even though the rhdh.installOperator param was set to false. 

Expected results:
If spec.rhdh.installOperator=false, the orchestrator CR's status should be true in this case. We should not be looking for resources we don't need.