Data Index must be prepared to support use cases where two workflows with the same name are deployed on different namespaces.
See: SRVLOGIC-340.

Solution to the problem is to prepare the Data Index to store the workflow namespace as part of the ProcessDefinition key, and not only the workflow name as it happens now.  Additionally, the GraphQL queries must be adapted to return that namespace on user demand as it happens with any other field. 

The Data Index will receive the workflow namespace as part of the ProcessDefinitionEvent

Note:

We must also consider how workflow instances are created, and managed from the Servlerless Workflows UI, by using the current Data Index Gateway API. And, if needed, the introduction of the namespace must be added there too.