aws_sagemaker_image_version - add support for alias fixes #35931

[psantus]

Description

Adds support for aliases in aws_sagemaker_image_versionresource.

It required to refactor resourceImageVersionRead because the AWS SDK doesn't have an Aliases field in DescribeImageVersionOutput.

Identical to #42609 but rebased on 6.0.0-beta.

Relations

Closes #35931

References

CreateImageVersion supports aliases
DescribeImageVersion doesn't return aliases
But we have a handy ListAliases API that helps

Output from Acceptance Testing

% cd ./internal/service/sagemaker && TF_ACC=1 SAGEMAKER_IMAGE_VERSION_BASE_IMAGE=<REDACTED>.dkr.ecr.us-west-2.amazonaws.com/terraform-test:latest AWS_PROFILE=<REDACTED> go test -v -run="TestAccSageMakerImageVersion_update" -count=1

2025/05/14 11:39:20 Creating Terraform AWS Provider (SDKv2-style)...
2025/05/14 11:39:20 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN   TestAccSageMakerImageVersion_update
=== PAUSE TestAccSageMakerImageVersion_update
=== CONT  TestAccSageMakerImageVersion_update
--- PASS: TestAccSageMakerImageVersion_update (113.39s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/sagemaker  117.300s

...

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.