Seed production-demo rows for a new minor line at branch cut

[kojiromike]

Summary

When a new minor release line is cut (e.g. v8.2.x), bump-tag.yml / IpMapBumper only advances rows whose branch_tag already matches a tag on that line. If no rows exist for the new line at the time of the first release, the bumper advances zero rows and the production-demo cells for the new line silently stay on the prior version (or stay empty).

The fix is to make seeding the production-demo rows for the new line part of the branch-cut step, so that the first bump-tag.yml run on the new line has rows to advance.

Why

• Today, seeding is implicit and only happens because someone remembers to add rows ahead of the first bump. When it is forgotten, the first release on a new line is invisible from the demo farm and there is no error -- the bumper reports success with zero rows touched.
• This is a silent failure mode that only surfaces when users (or the team) notice that demos for the new line are missing or stale.
• Branch cut is the natural place for this: the line is being created, the tag scheme for it is known, and the seeding can be deterministic.

Proposed

• Add a seeding step to the branch-cut tooling (or document it as a required step with a script in this repo) that inserts production-demo rows for the new line with branch_tag set to the initial tag for that line.
• Optionally, have bump-tag.yml warn (not fail) when it advances zero rows on a line that is expected to have rows, so the silent case becomes loud.

Reference

Related to the release-automation umbrella tracked in openemr/openemr-devops#706.

[bradymiller]

Superseded by the auto-derive bot (PRs #135 / #138 / #141 / #142 / #143).

The bot derives ip_map_branch.txt from upstream openemr/openemr's .github/release-targets.yml + per-rel-branch Dockerfile ARGs. New minor lines flow through naturally as soon as their entry lands in release-targets.yml on master — no manual production-demo row seeding required. The original concern (an unseeded minor would silently no-op against bump-tag.yml's MAJOR.MINOR match condition) is gone because bump-tag.yml itself is retired (PR #141) and the auto-derive bot has no such MAJOR.MINOR match condition.

Tracked in the umbrella issue openemr/openemr-devops#706 as moved-to-closed.