UI: The workflow name is not encoded in the URL when obtaining the definition.

### Describe the bug

If my workflow name contains permitted characters such as #, accessing its definition takes me to a path like this:
`/workflowDef/first#second`
This below searches for the workflow first by calling /workflowDef/first

However, if you use URL encoding, it works:
`/workflowDef/first%23second`
This below searches for the workflow first by calling /workflowDef/first%23second

Start at the UI entry point that constructs the `/workflowDef/{workflowName}` URL and reproduce the issue with a workflow name containing `#`. Trace how the name is placed in the path, then verify that the generated request preserves the complete name through URL encoding and that ordinary workflow names still work.

Written by the indexing model from the issue text.