Align deploy workflows on canonical GHCR image name

[Copilot]

The failing deploy / Build & Push Image job was pushing to a GHCR package path that did not match the image path used by deployment. This update standardizes both build and deploy workflows on a single image target to prevent registry permission/push mismatches.

• Root cause

  • Build steps were tagging/pushing ghcr.io/robticorg/robtic-staff while runtime deployment expects ghcr.io/robticorg/staff-system.

• Workflow alignment

  • Introduced a shared workflow env variable:
    • IMAGE_NAME: ghcr.io/robticorg/staff-system
  • Updated docker/metadata-action image source to use IMAGE_NAME instead of ${{ github.repository }}.
  • Updated reusable deploy workflow input image-name to the same IMAGE_NAME.

• Resulting invariant

  • All image-producing and image-consuming deploy paths now reference the same GHCR package.

env:
  IMAGE_NAME: ghcr.io/robticorg/staff-system

# build metadata
with:
  images: ${{ env.IMAGE_NAME }}

# reusable deploy workflow input
with:
  image-name: ${{ env.IMAGE_NAME }}

[robo38]

wtf