Add SageMaker HyperPod Karpenter Autoscaling Support

[allela-roy]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request
• The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.

Relates OR Closes #0000

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Description

Please briefly describe the changes proposed in this pull request.

This PR adds support for SageMaker HyperPod clusters with Karpenter-based autoscaling, enabling dynamic node provisioning for EKS-orchestrated workloads.
Changes made:

Resource Schema Updates:

Added auto_scaling attribute with mode and auto_scaler_type fields
Added cluster_role attribute for IAM role configuration

Documentation:
Updated documentation in /docs/resources/sagemaker_cluster.md to showcase functionality. Example:
Added examples/resources/awscc_sagemaker_cluster/sagemaker_cluster_eks_autoscaling.tf - Complete working example

[quixoticmonk]

Thank you for the contribution @allela-roy . AWSCC provider handlers are autogenerated based on the latest schema present on CloudFormation registry. The Handler and schema updates will be picked up automatically if that is what this PR is trying to accomplish. If yes, I would keep only the example documentation for the time being so that the next release of the provider will have those examples.

[quixoticmonk]

Seems like this is handled in https://github.com/hashicorp/terraform-provider-awscc/pull/2792/files#diff-f435b834eadf22492c218aa0bb4dcdaca09a4b6acc84eab05a82a679e1f93ecc except for the documentation. #2792

[wellsiau-aws]

@allela-roy - do you mind to update the PR to include only the documentation part since the resource schema is now available through auto-build. You can refer latest example PR for documentation here: https://github.com/hashicorp/terraform-provider-awscc/pull/2808/files