feat(datazone): support global_parameters in aws_datazone_environment_blueprint_configuration

[sAchin-680]

Add aws_datazone_environment_blueprint_configuration Resource

Rollback Plan

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

Changes to Security Controls

No changes to security controls (access controls, encryption, logging) are introduced in this PR.
All operations comply with the AWS DataZone API’s standard authorization model.

Description

This pull request introduces a new Terraform resource:

aws_datazone_environment_blueprint_configuration

This resource allows users to manage DataZone environment blueprint configurations within a specified domain.
It supports attributes such as:

• domain_id — The ID of the DataZone domain.
• environment_blueprint_id — The ID of the environment blueprint to configure.
• enabled_regions — The list of AWS regions where this configuration is active.
• global_parameters — A map of key-value pairs for configuring blueprint-specific parameters.

This addition improves the Terraform AWS Provider’s support for AWS DataZone by enabling blueprint-level automation and configuration management.

Relations

Closes #44836

References

Output from Acceptance Testing

% TF_ACC=1 go test -v -timeout 60m -run ^TestAccDataZoneEnvironmentBlueprintConfiguration_global_parameters$ ./internal/service/datazone


...

[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.

[github-actions]

⚠️ Our automation has detected the following potential issues with your pull request

---

❌ Changelog Entry Required (Click to expand)

The proposed change requires a changelog entry. Please see the Changelog Process section of the contributing guide for information on the changelog generation process.

Tip: This check is not triggered for draft pull requests, since the pull request number is not known until the pull request is opened and is required to create a changelog entry. Opening a pull request first as a draft, adding the requisite changelog entry file, and then marking the pull request as ready for review will prevent future warnings.