Domain can be deleted with running MLflow tracking server

### Product Version

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

### Issue Description

After launching MLflow tracking server, you can delete SageMaker domain without any warnings or issues. MLflow tracking server continue running and generating cost. It is not visible from the AWS Console, so you can delete it only using AWS CLI.
All other apps and spaces should be deleted before you can delete the SageMaker domain. This inconsistency confuses users and they sometimes forget to delete tracking server.

### Expected Behavior

SageMaker Studio domain deletion with running MLflow tracking server should cause an error.

### Observed Behavior

Domain is successfully deleted, while MLflow server continue running.

### Product Category

Experiments

### Feedback Category

Configuration and Setup

### Other Details

_No response_

No repository files, tests, or entry points are identified in the issue. Start by reproducing SageMaker Studio domain deletion with a running MLflow tracking server, using the AWS CLI as noted; done means deletion is blocked with an error rather than leaving the server running and incurring cost.

Written by the indexing model from the issue text.