JupyterLab Space Settings shows "No script" but default Lifecycle Script still executes

### Product Version

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

### Issue Description

In the new SageMaker JupyterLab Space UI, the "Lifecycle Configuration" dropdown does not seem to match reality when a default Lifecycle Script is associated with the User Profile. Despite configuring a default script for my user profile, when I create a new space "No script" is selected by default. Even more confusingly, when I start the app without touching the settings in the UI, **the configured default Lifecycle Script still runs, even though the UI shows "No script".**


### Expected Behavior

* When "No script" is selected in the UI, I expect no LCC script to run
* When a default LCC script is configured for the domain or user profile, I expect this script to be selected in the UI by default

### Observed Behavior

When a default LCC script is configured, the UI still shows "No script", but in fact the configured default script does execute

### Product Category

JupyterLab

### Feedback Category

User Interface

### Other Details

_No response_

Reproduce this in the SageMaker Studio JupyterLab Space UI with a default Lifecycle Script configured for the domain or user profile. Compare the displayed Lifecycle Configuration selection with the script that runs when the app starts; done means the UI accurately reflects the default and selecting "No script" prevents execution.

Written by the indexing model from the issue text.