Add standalone pipeline to rerun the last build of a given Jenkins test job

[sophia-guo]

There is no automated standalone mechanism to re-trigger a failed or unstable Jenkins test job externally — for example from a scheduled job, an upstream pipeline, or a remote Jenkins instance. The existing rerun logic is embedded inside JenkinsfileBase and only fires automatically within the same job run.

Solution:

Add buildenv/jenkins/rerunJobs.groovy, a standalone Jenkins declarative pipeline

Parameter	Required	Description
JOB_NAME	✅	Full Jenkins job name to inspect and rerun
SCM_REFERENCE	optional	Only proceed if the last build's CUSTOMIZED_SDK_URL contains this substring. When empty, the check is skipped entirely
MODE	optional	Set to RELAY to forward the rerun to the remote private Jenkins instead of running locally

[sophia-guo]

Rerun rules - under following rules, JOB_NAME could be any level of test jobs - parents job, child jobs, _rerun jobs. The strategy always produces the minimal possible rerun set — each level of _rerun progressively narrows down the failing tests, and we extract the already-computed minimal set from the description links rather than re-running the whole batch again.

• FAILURE / ABORTED → re-trigger with identical parameters (full rebuild).
• UNSTABLE → parse the build description for rerun links from addFailedTestsGrinderLink().
  - _custom links present → trigger one rerun per custom link in parallel; skip "failed test targets" link (redundant).
  - Only "failed test targets" link → trigger with TARGET=testList TESTLIST= override only.
  - Child job traversal — Note: If child jobs of parallel parent job status is FAILURE, the failed jobs will be rerun under failedjobname_rerun. For this case parents customized rerun link doesn't include any test failures of those rerun jobs. So those jobs rerun links will also be collected.