[BEAM-2675] Consolidate ValidatesRunner suite building into one file.

[jasonkuster]

Signed-off-by: Jason Kuster jasonkuster@google.com

Follow this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

---

This change reduces duplication in the ValidatesRunner tests and avoids the proliferation of additional files in favor of the minimum information necessary (runner name, maven args to run) for the test.

R: @kennknowles

Feel free to punt to someone else -- assigning to you as you've been working with the ValidatesRunner tests for a while.

[kennknowles]

TBH I think this makes the Jenkins job code a bit less discoverable. I would prefer that there be a central library that contains the logic, but each of the individual jobs still gets their own file.

[markflyhigh]

Python validates runner test in the future will have similar separated builds like java. So we may also want to leave a 'port' for Python.

[jkff]

This is likely quite a bit out of date; is it still relevant?

[jkff]

Closing per stale PR policy (60 days of inactivity), please reopen if needed.