MLFlow App and MLFlow Tracking Server URL Routing Issue

### Product Version

- [ ] Amazon SageMaker Studio Classic
- [x] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio

### Issue Description

When a MLFlow app and an MLFlow tracking server have the same name, only the configuration page for the MLFlow app can be accessed since they use the same url. For example, if the name used is "testing", then the url for the configuration page for both is "...sagemaker.aws/mlflow/testing", and this only directs (in my case) to the newer MLFlow app.

### Expected Behavior

When clicking on the MLFlow tracking server card on the MLFlow tracking server tab, I expect to be routed to a page about that MLFlow tracking server, including information about the version ARN and meta data. Even when that tracking server has the same name as a MLFlow app.

### Observed Behavior

When clicking on the MLFlow tracking server card on the MLFlow tracking server tab, and the name of that tracking server is the same as a MLFlow app's name, I am routed to a page about the MLFlow App with the same name. I am not routed to a page about the MLFlow tracking server.

### Product Category

Experiments

### Feedback Category

User Interface

### Other Details

I can see that both tabs (new MLFlow App and older MLFlow Tracking Server) use the url "...sagemaker.aws/mlflow/name-of-app-or-server" so when they have the same name, there's no way to differentiate.

No repository files, tests, or entry points are named. Start by reproducing the collision in Amazon SageMaker Studio with an MLFlow app and tracking server sharing a name, then inspect the routing behavior for both cards. Done means each card reaches its corresponding configuration or tracking-server details page despite identical names.

Written by the indexing model from the issue text.