Sagemaker Studio JupyterLab space encounters 'Lifecycle Config execution failed' despite having 'No script' selected

### Product Version

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

### Issue Description

I am attempting to launch a Jupyterlab space. I have a custom LCC that fails with Sagemaker Distribution Image 3.5.0.
Upon removing the selected LCC (i.e. selecting 'No Script') and trying again, I still get the same error with the same LCC ARN.

### Expected Behavior

Expected behavior is to not encounter an LCC failure code when selecting 'No Script'.

### Observed Behavior

_No response_

### Product Category

JupyterLab

### Feedback Category

Error Handling and Debugging

### Other Details

_No response_

No repository files or tests are identified in the report. Reproduce the failure in Amazon SageMaker Studio JupyterLab with SageMaker Distribution Image 3.5.0: compare launching with the custom lifecycle configuration selected versus selecting “No Script,” and verify whether the same lifecycle configuration ARN and failure code persist. Done means confirming the cause or recording a reproducible result with the relevant error details.

Written by the indexing model from the issue text.