SageMaker Studio domain default Lifecycle Configurations

### Name of the resource

AWS::SageMaker::Domain

### Resource name

_No response_

### Description

SageMaker Studio Lifecycle configurations can be added to a SageMaker Domain with the CLI, but not with CloudFormation.

With CLI:
```bash
aws sagemaker update-domain --domain-id \
--default-user-settings '{
"JupyterServerAppSettings": {
"DefaultResourceSpec": {
"LifecycleConfigArn": "arn:aws:sagemaker:::studio-lifecycle-config/",
"InstanceType": "system"
},
"LifecycleConfigArns": [
"arn:aws:sagemaker:::studio-lifecycle-config/"
]
}
}'
```

In CFN there is [no support](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-sagemaker-domain-jupyterserverappsettings.html) for the `LifecycleConfigArns` property. Only specifying `DefaultResourceSpec` does not through an error, but fails when booting up the JupyterServerApp as users try to access Studio.

### Other Details

_No response_

Start with the AWS::SageMaker::Domain JupyterServerAppSettings documentation linked in the issue and compare its CloudFormation properties with the shown aws sagemaker update-domain command. Confirm how LifecycleConfigArns should be represented alongside DefaultResourceSpec. Done means CloudFormation supports this property and users can configure the domain's default Studio lifecycle configurations.

Written by the indexing model from the issue text.