fix(ci): remove tag fallback in merge flow

[DerekRoberts]

Removes the inputs.tag || github.sha fallback from merge.yml, so every deploy uses one explicit tag.

• Deploy (TEST), Deploy (prod) and Promote Images now use ${{ github.sha }}. That is the merge-commit tag the Resolve Images job creates from the digest image-tracker resolves.

• Removes the unused workflow_dispatch tag input and the two if: ${{ !inputs.tag }} step gates. The input predates chore(ci): pin bcgov action suites to v0.8.0 / v0.3.1 and move off standalone actions #497 and has never been used (0 dispatch runs). A manual dispatch now resolves and deploys the dispatched commit the same way a push does.

• Java

• Py

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused workflow changes consistently implement the stated single-tag deployment behavior.

Review effort: Balanced
Findings: None

What changed in this PR

Removes the obsolete manual tag override so merge deployments consistently use the resolved image tagged with the triggering commit SHA.

Changes:

• Removes the workflow_dispatch tag input and conditional gates.
• Uses ${{ github.sha }} for test, production, and image promotion.

File	Description
.github/​workflows/​merge.yml	Standardizes merge-flow image resolution, deployment, and promotion on the commit SHA.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.