Issue
publisher.generateRunInfoFiles() pushes run-info values by calling infraUtils.newStringJobParam twice per key (empty then populated). This is stringly-typed, non-DRY, and obscures data flow.

Steps to reproduce
1. Review publisher.generateRunInfoFiles() in vars/publisher.groovy.
2. Observe multiple newStringJobParam calls for DATA_* values.

Expected result
Run-info data is persisted in a structured context artifact and passed explicitly.

Actual result
Values are propagated via repeated newStringJobParam calls with hidden side effects.

Plan

• Define a run-info context schema (JSON) and persist once per build.
• Archive the JSON as an artifact and expose a single build param if needed.
• Update consumers to read from the run-info JSON or new context API.
• Remove redundant newStringJobParam calls and keep a single source of truth.