[Bug]: Re-enable GoUsingJava xlang suites

[tvalentyn]

What happened?

There is evidence that Go-Using-Java XLang scenario might not we working well. Once we can prioritize this, we should fix and re-enable the following suites (which have been perma-red):

• https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_GoUsingJava_Dataflow.yml
• GoUsingJava scenarios in https://github.com/apache/beam/actions/workflows/beam_PostCommit_XVR_Direct.yml , see: Disable permared go xlang tests. #32423

cc: @lostluck
cc: @chamikaramj

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[github-actions]

This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

[github-actions]

This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.

[liferoad]

Running https://github.com/apache/beam/actions/runs/17247614855