fix: upgraded build and push yaml (MAPCO-9842)

[roicohen326]

Question	Answer
Bug fix	✖
New feature	✖
Breaking change	✖
Deprecations	✖
Documentation	✖
Tests added	✖
Chore	✖

[Copilot]

Pull request overview

Updates the tag-triggered GitHub Actions workflow to use MapColonies “shared-workflows” composite actions and to parameterize registry/token values via secrets, supporting a more reusable and centrally maintained release pipeline.

Changes:

• Switch from repo-specific actions to MapColonies/shared-workflows/actions/* equivalents for login, build/push, and artifacts update.
• Replace hard-coded ACR registry URL with ${{ secrets.ACR_URL }} and adjust action inputs (e.g., context, artifact_name, artifact_tag, type).
• Configure checkout and artifacts update steps to use ${{ secrets.GH_PAT }}.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

github_token is set to a PAT (secrets.GH_PAT). If the action only needs repo-scoped access, use GITHUB_TOKEN so access is constrained by the workflow permissions and can’t exceed what the job declares.

Suggested change

	github_token: ${{ secrets.GH_PAT }}
	github_token: ${{ github.token }}

[Copilot]

This action is referenced by a movable tag. To reduce supply-chain risk, consider pinning to an immutable commit SHA (or another immutability mechanism your org uses) instead of a tag name.

[Copilot]

This action is referenced by a movable tag. To reduce supply-chain risk, consider pinning to an immutable commit SHA (or another immutability mechanism your org uses) instead of a tag name.

[Copilot]

This action is referenced by a movable tag. To reduce supply-chain risk, consider pinning to an immutable commit SHA (or another immutability mechanism your org uses) instead of a tag name.

[Copilot]

actions/checkout is configured to use a long-lived PAT (secrets.GH_PAT). If a PAT isn’t strictly required here, prefer the built-in GITHUB_TOKEN (or omit with.token) so the workflow token stays least-privileged and scoped by the workflow permissions block. If a PAT is required, consider documenting why and ensuring it’s minimally scoped (e.g., contents only).

Suggested change

	with:
	token: ${{ secrets.GH_PAT }}