[Operator] Cluster-Scoped Supporting Services in SonataFlow Operator

Add support for handling services deployment in cluster scope instead of only namespace scope.

KOGITO-9740 and KOGITO-9742 deal with Data Index and Job Services deployment in namespace scope. This means that all workflows deployed within the same namespace can interact only with Data Index and Job Services deployed in the current context.

Goals:

• Users can choose where to deploy the supporting services
• Users can configure a SonataFlowPlatform to make every workflow in the current context connect to a specific supporting service in another context
• By default, workflows should connect within the same context
• The operator should have a global configuration where every deployed SonataFlowPlatform should inherit. For example, the Data Index/Jobs Service where the workflow should connect.

This setup enables the following topologies:

1. One Data Index and Jobs Service per cluster, having all workflows connected there
2. One Data Index and Jobs Service per namespace, so users can shard their workflows data in the local scope
3. A mix configuration where a group of workflows deployed in "n" namespaces can connect to a single supporting services deployment.