Operator support to handle the same workflow name in different namespaces

[masayag]

Description

In a cluster with SonataflowClusterPlatform CR enabled, when a workflow is installed in namespace A, in which the SonataflowClusterPlatform points to the SonataflowPlatform, and another workflow with the same name is installed in another cluster, both workflows do not co-exist in the same Data-Index.
Instead, the latter workflow overrides the details of the former, causing requests intended for the first workflow to get to the second one.

Implementation ideas

K8s uses namespace+name as a unique identifier of resources.
A similar approach can be taken with Data-Index.