tech-debt: refactor mq data and resources to use different Read methods

[anGie44]

Community Note

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

Relates #18819
Relates #7926

Output from acceptance testing:

In progress

[bflad]

One missing d.Set() for broker_id in the data source, but otherwise looks good

Output from acceptance testing:

--- PASS: TestAccAWSMqBroker_rabbitmq (627.27s)
--- PASS: TestAccAWSMqBroker_clusterRabbitMQ (712.08s)
--- PASS: TestAccAWSMqBroker_throughputOptimized (774.35s)
--- PASS: TestAccAWSMqBroker_EncryptionOptions_UseAwsOwnedKey_Enabled (1096.01s)
--- PASS: TestAccAWSMqBroker_tags (1144.48s)
--- PASS: TestAccAWSMqBroker_ldap (1146.03s)
--- PASS: TestAccAWSMqBroker_disappears (1154.52s)
--- PASS: TestAccAWSMqBroker_EncryptionOptions_KmsKeyId (1160.86s)
--- PASS: TestAccAWSMqBroker_EncryptionOptions_UseAwsOwnedKey_Disabled (1166.05s)
--- PASS: TestAccAWSMqBroker_basic (1190.20s)
--- PASS: TestAccAWSMqBroker_updateSecurityGroup (1341.58s)
--- PASS: TestAccAWSMqBroker_updateEngineVersion (1362.09s)
--- PASS: TestAccAWSMqBroker_updateUsers (1545.13s)
--- PASS: TestAccAWSMqBroker_allFieldsCustomVpc (1775.76s)
--- PASS: TestAccAWSMqBroker_allFieldsDefaultVpc (1820.07s)

[ghost]

This has been released in version 3.37.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!