Request support for SAM CDK Migration with SAM Transform Template.

### Describe the feature

Request support for SAM CDK Migration with SAM Transform Template.

### Use Case

Problem. Couldn't replicate CDK Synth and what artifact to use.

Migrating to CDK won't resolve resource limit problem. CDK Migrate - Will generate L1s. Want L2s and L3s for high level constructs.

Restructure for code base construct. CDK Migrate is based on IAC Generator. Can scan your account and create managed stacks out of the resources you find.
Console - IAC generator - Pick what you don't want to touch. Get all together in one CFN template for stateless stuff. Will turn into a managed stack.

CDK Migrate is based on IAC generator. Will have to go original stack to update with all retention deletion policies
set to retain, then delete the stack in order to adopt it into a new stack. This will be a mandatory step.

Adopt stateless stuff into a stack. Adopt stack into CDK function. Most risk. Go onto CDK and move resources from nested stack.

Cons: Up against resource limits that has transforms which goes against resource limit. Use them together in transition?
Customer is using SAM Transform Template. Complicates for migration for Transform and CDK Migrate.

### Proposed Solution

_No response_

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.146.0

### Environment details (OS name and version, etc.)

Python

The issue does not identify any files, tests, or entry points to inspect, and it provides no proposed solution. First clarify the intended SAM Transform and CDK Migration behavior, the artifacts involved, and the acceptance criteria before looking for an implementation location.

Written by the indexing model from the issue text.