(core): speed up process for adding L1 constructs to aws cdk for newly released cloudformation resources

### Describe the feature

This feature request proposes accelerating the process of adding L1 constructs to AWS CDK for newly supported CloudFormation resources. Currently, it takes 2-3 weeks for these constructs to be available after the resource specification is updated.

### Use Case

Speeding up this process would allow us to leverage new AWS resources quicker within their Infrastructure. This is particularly critical for teams that rely heavily on the CDK for deploying their AWS resources. Also it avoids us to workaround the issue by implementing custom resources..

Faster integration would reduce the time between AWS CloudFormation announcements and actionable use in the CDK.

### Proposed Solution

Review the current deployment cycle and explore opportunities to speed up the generation and deployment of L1 constructs.

### Other Information

This request builds on recent feedback regarding the AWS::SageMaker::MlflowTrackingServer resource addition: https://github.com/aws/aws-cdk/issues/31112#issuecomment-2289765115

### Acknowledgements

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

### CDK version used

2.151.0

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

macOS

Start by tracing the current process for generating and deploying L1 constructs after the CloudFormation resource specification is updated. Review the deployment cycle described in the issue and the related AWS::SageMaker::MlflowTrackingServer discussion. Done means identifying and implementing a way to shorten the current 2–3 week delay, with the resulting process validated.

Written by the indexing model from the issue text.