[BEAM-7636] Migrate SqsIO to AWS SDK for Java 2

[cmachgodaddy]

This PR is adding SqsIO v2 to amazon-web-services2 submodule, and which uses AWS SDK V2. There are a few changes comparing to SqsIO V1:

1. Adding SendMessageRequestCoder, since it's not serializable in SDK V2
2. Adding MessageCoder, since it's not serializable in SDK V2
3. Adding a custom SqsMessage, since the attributes of the Message is not serializable, and to return attributes to downstream users. We will get an exception DefaultSdkContructionMap is not serializable if we don't do this.
4. Refactor unit test: have a separate class for EmbeddedSqlServer
5. Remove SqsConfiguration class, and add withXXX methods() to take in AwsSecretsProvider

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Post-Commit Tests Status (on master branch)

Lang	SDK	Apex	Dataflow	Flink	Gearpump	Samza	Spark
Go		---	---		---	---
Java
Python		---			---	---
XLang	---	---	---		---	---	---

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website
Non-portable
Portable	---		---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

[aromanenko-dev]

Thanks for contribution!
Please, run gradlew spotlessApply before committing.

[aromanenko-dev]

Run Java PreCommit

[aromanenko-dev]

Thanks! I did a review mostly over new added part and I expect that all other functionality/tests are left "as it was before".
Also, I think that @JohnRudolfLewis, as initial author of SqsIO, could be interested in review too.

[aromanenko-dev]

Does it send message synchronically? Would it make sense to batch the messages of the whole bundle and send them as a batch for better performance?

[cmachgodaddy]

Yes, that make send, but then our API has to take in SendMessageBatchRequestEntry, instead of SendMessageRequest. Now, there are three ways to deal with this:

1. Take in SendMessageBatchRequestEntry, instead of SendMessageRequest. This way will impact all of the existing users
2. Keep the existing api, which take in SendMessageRequest, and convert it to SendMessageBatchRequestEntry manually in our IO. Bascially, mapping each attribute of SendMessageRequest to SendMessageBatchRequest's
3. Add another API, called writeBatch, and this one takes in SendMessageBatchRequestEntry, backward compatibility support
   I prefer [BEAM-22] Support Unbounded PCollections in same-process execution #3, since it makes a clear distinction, users know what they are doing, and nobody get "hurt" ;-)
   @aromanenko-dev let me know what you think?

[aromanenko-dev]

I'm ok to keep it as it was before for now. Perhaps, it would make sense to add TODO comment for the future about that.

[aromanenko-dev]

Please, take a look on failing tests in Java PreCommit job on Jenkins

[aromanenko-dev]

@cmachgodaddy Please, fix Spotless issue.

[aromanenko-dev]

@cmachgodaddy There are 2 failed "old" SqsIOTest tests. I think it's related to using the same host/port for EmbeddedSqsServer. Could you fix this, please?
PS: other fails are not related to this PR, I think

[aromanenko-dev]

Run CommunityMetrics PreCommit

[aromanenko-dev]

Run Python PreCommit

[cmachgodaddy]

Run Python PreCommit

[aromanenko-dev]

Thanks, LGTM