chore: migrate to new docker publish workflow

[Rocket-Quack]

Information about bug

🔄 Migration Required: Update Docker Publish Workflow Reference

This repository is currently using the legacy Docker publish workflow, which has been replaced with a new standardized workflow.

---

📦 What changed

A new workflow is now used for publishing Docker images:

• New workflow:
  https://github.com/frappe/frappe_docker/blob/main/.github/workflows/core-build-stable.yml

The previous workflow is still functional for now but is considered legacy and will be removed once all dependent repositories have been migrated.

---

⚠️ Required change

Please update all references in this repository from the old workflow to the new workflow.

• Old workflow:
  https://github.com/frappe/frappe_docker/blob/main/.github/workflows/build_stable.yml

• New workflow:
  https://github.com/frappe/frappe_docker/blob/main/.github/workflows/core-build-stable.yml

---

🧪 Backward compatibility

• The old workflow remains temporarily supported
• No immediate breaking changes
• Migration can be performed safely at any time

---

🚀 Action required

• Identify references to the old workflow in this repository
• Replace them with the new workflow
• Verify Docker publishing still works as expected

---

🗓️ Deprecation note

The old workflow will be removed once all repositories have been migrated.

Migration progress is tracked here:
frappe/frappe_docker#1884

---

🙌 Thanks

This migration helps unify and simplify our CI/CD pipeline across repositories.

Module

other

Version

Every Version what uses Docker Frappe to Build Images

Installation method

docker

Relevant log output / Stack trace / Full Error Message.

Code of Conduct

• I agree to follow this project's Code of Conduct