fix(ci): publish container images from the main CI workflow

[Copilot]

Container publishing now runs as the final stage of checks.yml for successful pushes to main, replacing the standalone workflow_run workflow. Deployment and migration documentation now describe the automated path.

• CI publishing

  • Move GHCR build/push into publish-container-image in checks.yml
  • Require successful source-affecting lint, build, unit, integration, and post-test stages
  • Support intentional skipped checks when no source-affecting files changed
  • Restrict publishing to push events on refs/heads/main
  • Remove publish-container-image.yml

• Workflow coverage

  • Add a unit test validating dependencies, branch/event gating, source-change behavior, and legacy workflow removal

• Documentation

  • Add deployment publishing behavior in docs/DEPLOYMENT.md
  • Add migration rationale and behavior in docs/CI-MIGRATION.md
  • Update production deployment documentation link

if: >-
  always() && github.event_name == 'push' && github.ref == 'refs/heads/main' &&
  needs.changes.result == 'success' &&
  (needs.changes.outputs.src != 'true' || (...checks succeed...)) &&
  needs.post-tests.result == 'success'

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0ada192

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR