New Sagemaker Studio auto-shutdown doesn't autoshutdown

### Product Version

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

### Issue Description

Based on this notice:

https://aws.amazon.com/about-aws/whats-new/2024/09/amazon-sagemaker-studio-automatic-shutdown-idle-applications/

Sagemaker now supports auto-shutdown on idle jupyterlab (not classic) and code editor without the configuration of lifecycle configurations. I've gone through the instructions and enabled idle shutdown on the entire domain. However, none of my machines are shutting down automatically. It is set to 2.8 hours of idle, and I am using Sagemaker Distribution 2.0. I do note that it has a fairly long list of conditions for idle shutdown:

```
For Code Editor applications, the instance is considered idle when the following conditions are met:

1. No text file or notebook changes
2. No files being viewed
3. No interaction with the terminal
4. No background processes running
5. No notebook kernels processing
6. No unsaved work

```
If I close out the brower tab without any extra processes running I assume conditions 1, 2, 4, 5 are satisfied. If I enable auto-save in VSCode I assume condition 6 is met. I'm not sure what 2 means for 'viewed'. I leave the tabs open and close the browser window, so I assume they are not being 'viewed' unless 'viewed' is defined as having a file in focus server-side. Either way, I did simply stop the machine and start it without opening anything and still doesn't work. I even created an entire machine from scratch and never once opened the machine and it's still up.

Are there some cloudwatch logs or anything I can do to find out why it's not shutting down? Thanks.

### Expected Behavior

It shuts down after 2.8 hours.

### Observed Behavior

It stays up constantly.

### Product Category

_No response_

### Feedback Category

_No response_

### Other Details

_No response_

The report names no repository files, tests, or entry points; begin with the linked AWS announcement and the stated Studio configuration, including the 2.8-hour timeout and SageMaker Distribution 2.0. Done would require identifying the cause of the instance remaining active and documenting a reproducible fix or confirmed service behavior.

Written by the indexing model from the issue text.