AWS::Sagemaker::StudioLifecycleConfiguration (Lifecycle Configuration for Sagemaker Studio Notebooks)

### Name of the resource

Other

### Resource name

AWS::Sagemaker::StudioLifecycleConfiguration

### Description

Resource for supporting Lifecycle Configuration management on Sagemaker Studio Notebooks. Lifecycle configuration is vital to control SageMaker studio spend via auto-idle shutdown or for configuration and automated integration of private package management and git repositories especially in larger deployments across many AWS Accounts.

This resource type needs to provide the ability to attach lifecycle configuration to both the jupyter server or an image kernel and at the user level or at the domain wide-level (all users). Package command support, drift detection and resource import would be great bonuses!

Suggested Structure:

```yaml
StudioLifecycleConfiguration:
Type: AWS::Sagemaker::StudioLifecycleConfiguration
Properties:
DomainId:
Scope: [ Domain | User ]
Type: [ Server | Kernel ]
Name:
Script:

```

### Other Details

Sagemaker Studio Lifecycle Management APIs:
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/create-studio-lifecycle-config.html
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/describe-studio-lifecycle-config.html
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/delete-studio-lifecycle-config.html

Attachment/Detachment against Sagemaker Studio Domain:
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/update-domain.html

Lifecycle Configuration Examples provided by AWS:
https://github.com/aws-samples/sagemaker-studio-lifecycle-config-examples

General overview of Studio Lifecycle Configuraiton:
https://aws.amazon.com/blogs/machine-learning/customize-amazon-sagemaker-studio-using-lifecycle-configurations/

Start with the linked SageMaker create, describe, and delete Studio lifecycle configuration API docs and the update-domain API, then compare the AWS lifecycle configuration examples. Define the resource around the proposed DomainId, Scope, Type, Name, and Script properties; completion should cover lifecycle configuration attachment behavior, with package commands, drift detection, and import as optional bonuses.

Written by the indexing model from the issue text.