Description of the problem:
When a sonataflow CR with associated configmaps is created in a separate namespace from an existing sonataflow platform CR, the operator creates a new sonataflow platform CR in the same namespace as the sonataflow CR. This causes issues with deployed workflows such as MTA, as incorrect values are added to associated configmaps, and attributes that should appear in the config map are missing.

How reproducible: 100%

Steps to reproduce:

1. Deploy a workflow on a cluster with Sonataflow enabled, but create the sonataflow CR in a separate namespace than the existing sonataflow platform CR.

Actual results: Issues with deploying the workflow - incorrect values are inserted into the workflow's properties configmap, and required attributes are not automatically added to the configmap as well.

Expected results: Even if the SFP CR and the SF CR are in separate namespaces, the deployment should work as expected.