MSK configuration data source should accept longer name

[xiaxuantan]

Description

We created some MSK configs longer than 64 characters. But when we tried to read them via data source, errors occurred: Error: expected length of name to be in the range (1 - 64). I've verified that the longest name for configuration should be 128.

Relations

Closes #0000

References

Output from Acceptance Testing

$ make testacc TESTS=TestAccKafkaConfigurationDataSource_longestName PKG=kafka
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/kafka/... -v -count 1 -parallel 20 -run='TestAccKafkaConfigurationDataSource_longestName'  -timeout 360m
=== RUN   TestAccKafkaConfigurationDataSource_longestName
=== PAUSE TestAccKafkaConfigurationDataSource_longestName
=== CONT  TestAccKafkaConfigurationDataSource_longestName
--- PASS: TestAccKafkaConfigurationDataSource_longestName (25.83s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/kafka	30.466s

...

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

[ewbankkit]

LGTM 🚀.

[ewbankkit]

@xiaxuantan Thanks for the contribution 🎉 👏.
I removed any name length validation to match the corresponding resource.

[github-actions]

This functionality has been released in v5.32.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. Thank you!

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