resource/aws_m2_environment: Add Mainframe Modernization Environment resource

[drewtul]

Description

Add resource for managing AWS Mainframe Modernization environments.

Relations

Depends on #35309.
Closes #35379.

Output from Acceptance Testing

==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/m2/... -v -count 1 -parallel 20 -run='TestAccM2Environment_'  -timeout 360m
=== RUN   TestAccM2Environment_basic
=== PAUSE TestAccM2Environment_basic
=== RUN   TestAccM2Environment_full
=== PAUSE TestAccM2Environment_full
=== RUN   TestAccM2Environment_update
=== PAUSE TestAccM2Environment_update
=== RUN   TestAccM2Environment_highAvailability
=== PAUSE TestAccM2Environment_highAvailability
=== RUN   TestAccM2Environment_efs
=== PAUSE TestAccM2Environment_efs
=== RUN   TestAccM2Environment_fsx
=== PAUSE TestAccM2Environment_fsx
=== RUN   TestAccM2Environment_disappears
=== PAUSE TestAccM2Environment_disappears
=== RUN   TestAccM2Environment_tags
=== PAUSE TestAccM2Environment_tags
=== CONT  TestAccM2Environment_basic
=== CONT  TestAccM2Environment_efs
=== CONT  TestAccM2Environment_update
=== CONT  TestAccM2Environment_highAvailability
=== CONT  TestAccM2Environment_full
=== CONT  TestAccM2Environment_disappears
=== CONT  TestAccM2Environment_tags
=== CONT  TestAccM2Environment_fsx
--- PASS: TestAccM2Environment_disappears (368.57s)
--- PASS: TestAccM2Environment_basic (423.01s)
--- PASS: TestAccM2Environment_highAvailability (433.89s)
--- PASS: TestAccM2Environment_full (462.32s)
--- PASS: TestAccM2Environment_efs (473.90s)
--- PASS: TestAccM2Environment_update (818.10s)
--- PASS: TestAccM2Environment_fsx (1144.78s)
--- PASS: TestAccM2Environment_tags (1319.07s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/m2 1324.493s
...

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

Thank you for your contribution! 🚀

Please note that typically Go dependency changes are handled in this repository by dependabot or the maintainers. This is to prevent pull request merge conflicts and further delay reviews of contributions. Remove any changes to the go.mod or go.sum files and commit them into this pull request.

Additional details:

• Check open pull requests with the dependencies label to view other dependency updates.
• If this pull request includes an update the AWS Go SDK (or any other dependency) version, only updates submitted via dependabot will be merged. This pull request will need to remove these changes and will need to be rebased after the existing dependency update via dependabot has been merged for this pull request to be reviewed.
• If this pull request is for supporting a new AWS service:
  • Ensure the new AWS service changes are following the Contributing Guide section on new services, in particular that the dependency addition and initial provider support are in a separate pull request from other changes (e.g. new resources). Contributions not following this item will not be reviewed until the changes are split.
  • If this pull request is already a separate pull request from the above item, you can ignore this message.

[meetreks]

Thanks Kit, really helpful.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.