Use ListSecretVersionIds when secret is write-only

[josnyder-2]

Description

Presently, the provider reads secrets from AWS under all circumstances, even when it is configured in write-only mode by use of secret_string_wo. As a result, it is not possible for an unprivileged user who is working with a statefile that has write-only secrets to perform a terraform plan -refresh=true.

This pull request modifies the behavior so that—when in write-only mode—we use ListSecretVersionIds instead of GetSecretValue.

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

[justinretzolk]

Relates #42383
Relates #43579