Fix PostCommit TransformService Direct job

[Amar3tto]

Fixes #30960

Successful run: https://github.com/Amar3tto/beam/actions/runs/13992581500

---

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

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• 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.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

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.

[github-actions]

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

R: @jrmccluskey for label python.

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

[Amar3tto]

R: @damccorm

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[Abacn]

This was caused by #34073, specifically this line: https://github.com/apache/beam/pull/34073/files#diff-4d72b1d96a597dfd42528b37549162b5124462b5c8bf6655d9cef91d9b3c8ac7L58

cc: @robertwb in what scenario it needed to be localhost?

[robertwb]

"[::]" was failing tests sometimes, perhaps do to inavailability (or flakiness) of ipv6?

[robertwb]

0.0.0.0 might assume/require ipv4 though