Roll back disabling of aws_accessanalyzer_analyzer_invalid_type linter rule after it's been updated with new analyzer types

[acwwat]

Description

While working on #43138, the linter rule aws_accessanalyzer_analyzer_invalid_type was failing on the PR because the list of supported analyzer type has not been updated in the linter role code. As a temporary workaround, I've disabled the rule as part of the PR. This issue is opened so that I can roll back the linter configuration once the code has been updated (automatically).

Important Facts and References

See #43138 for details.

Would you like to implement a relevant change?

Yes

[github-actions]

Community Guidelines

This comment is added to every new Issue 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 Issue 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 Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.

[acwwat]

Link to linter code for convenience: https://github.com/terraform-linters/tflint-ruleset-aws/blob/master/rules/models/aws_accessanalyzer_analyzer_invalid_type.go