The Serverless Workflow UI must be prepared to support use cases where two workflows with the same name are deployed in different namespaces.
See: SRVLOGIC-340.

For example, one of the implicances at the Servlerless Workflows Workflows UI, is that, if  "my-workflow" was deployed in namespace1 and namespace2, at the time of creating a new instance, users must be conscious about which workflow definition will be created.

See attached screenshots.

Implementation notes:

1. We must analyze if the change has impact on the monitoring screen calculation.
2. We must analyze if the change has impact on the different invocations to the DI Gateway API to manipulate the WF instances. (hopefully not,  if I don't real wrong, all invocations are based on the serviceUrl only)