Description of the problem:
In the current version of the orchestrator go operator 1.5.0-2025-03-03, the default orchestrator CR in the CSV assumes that an eventing broker already exists and generates default values fir it, i.e.
 

platform: 
  eventing:   
    broker:       
      name: my-knative       
      namespace: knative

 
If no kafka or in memory broker already exists, this is propogated down to the sonataflow-platform resource and causes deployment failures  due to the missing resources (the job service never deploys due to a missing resources). Even if the user removes the eventing field from the orchestrator resource before applying it, the orchestrator CR is still generated with populated empty values and the job service still does not deploy. 

The eventing field should be optional in the orchestrator CR. A "enabled: true/false" field should be added. If true, look for the eventing resources in the supplied namespace, if false, the installation should continue without it. The user can add it directly to the SF resources if required.

How reproducible: 100%

Steps to reproduce:

1. See above.

Actual results: See above

Expected results: See above.