TextIOReadTest creates pipelines with non-unique application names

[kennknowles]

The test TextIOReadTest uses a loop to create a few tests within a single test method. This results in a pipeline with non-unique applied transform nodes.

Perhaps the best way to fix this is to use a JUnit Paramaterized test suite, or multiple. It does seem that the test is basically doing the full product of empty/tiny/large with various compression types.

Imported from Jira BEAM-2632. Original Jira may contain additional context.
Reported by: kenn.

[Subramanya-Veeregowda]

Hi, I’d like to work on this issue.

From my understanding, the issue is caused by pipelines being created in a loop with non-unique names.

Instead of refactoring the test structure (like the previous PR), I plan to fix this by assigning a unique job name to each pipeline instance.

Please let me know if this approach looks good.