Python PTransform wrapper for AWS SQS

[prodriguezdefino]

Completes the work started on #34327 to expose the SQS read functionality to the Python SDK.

Added integration tests for the Direct Runner executed as part of a post commit suite. Tested execution of the new GitHub workflow in the forked repository, see link.

---

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[prodriguezdefino]

fixes #34326

[Abacn]

(question to @ahmedabu98) Shall we add this external transform to auto wrapper?

[ahmedabu98]

Yeah this looks like something that can be automated using standard_expansion_services.yaml

[ahmedabu98]

and the integration test below can dynamically generate and use the transform with ExternalTransformProvider

[prodriguezdefino]

quick question, can the integration test use the newly generated transform instead of the ExternalTransformProvider? given the dependencies the new Python wrapper should already be in place, is that right?

[prodriguezdefino]

Ok, I made the changes to make the IT use the ExternalTransformProvider. Thanks for for the pointers.

[ahmedabu98]

I think it depends -- some test environments won't set up the SDK before testing, i.e. it won't run the code that generates the wrapper file. So it's safer to use ExternalTransformProvider

Thanks for making those changes

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @jrmccluskey for label python.
R: @ahmedabu98 for label java.
R: @Abacn for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[ahmedabu98]

Thanks for this change @prodriguezdefino, left some comments

I'm curious, how did you find the instructions? any feedback?

[ahmedabu98]

You can automate this part using our existing utils. Steps:

1. Create a new pytest marker here
2. Mark your new test in xlang_sqsio_it_test.py with pytest.mark.
3. Follow these instructions:

   beam/sdks/python/test-suites/xlang/build.gradle

   Lines 24 to 25 in 0536dc6

   	// To run tests that use another expansion service, create a new CrossLanguageTask with the
   	// relevant fields as done here, then add it to `xlangTasks`.

[ahmedabu98]

If you name the new task "awsCrossLanguage" for example, it will create a new gradle task ":sdks:python:test-suites:direct:py<version>:awsCrossLanguagePythonUsingJava" that you can reference in sdks/python/test-suites/direct/build.gradle