Update docs related to v1 vs v2 AWS resources

[adamconnelly]

Description of the change

I've removed the experimental notes against the new v2 resources and added a deprecation note against the v1 resources. I haven't actually marked the old resources as deprecated yet because I don't want to immediately start generating warnings in logs for customers until we're completely certain we want to deprecate the old resources.

Type of change

• [ ] Bug fix (non-breaking change that fixes an issue)
• [ ] New feature (non-breaking change that adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Documentation (non-breaking change that adds documentation)

Checklists

Development

• [x] Lint rules pass locally
• [ ] The code changed/added as part of this pull request has been covered with tests
• [ ] All tests related to the changed code pass in development
• [ ] Examples for new resources and data sources have been added
• [ ] Default values have been documented in the description (e.g., "Dummy: (Boolean) Blah blah. Defaults to false.)
• [x] If the action fails that checks the documentation: Run go generate to make sure the docs are up to date

Code review

• [x] This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• [x] Pull Request is no longer marked as "draft"
• [ ] Reviewers have been assigned
• [ ] Changes have been reviewed by at least one other engineer
• [x] The target branch is future unless the change is going directly into production

[marcinwyszynski]

Task linked: CU-2n0acc0 [AWS Attachments] Mark old TF resources and properties as deprecated