feat: add production and staging deployment workflows

[levivannoort]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Queued	View Logs	Preview URL

Tip

Every Git commit and branch gets its own deployment URL automatically

[greptile-apps]

Greptile Summary

This PR adds dedicated deployment workflows for cloud console releases. The main changes are:

• New production workflow that builds appwrite/console-cloud and opens a declarative deployment PR.
• New staging workflow that builds appwrite/console-cloud-stage and updates the declarative staging config.
• Legacy cloud image jobs removed from the publish workflow.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
.github/workflows/production.yml	Adds the production build and declarative deployment workflow with PR-based promotion.
.github/workflows/staging.yml	Adds the staging build and declarative deployment workflow with direct staging config updates.
.github/workflows/publish.yml	Removes the legacy cloud publish jobs while keeping the remaining publish workflow.

_{Reviews (2): Last reviewed commit: "fix(deployment): update workflows to cre..." | Re-trigger Greptile}

[greptile-apps]

Release Aliases Stop Updating

The old release job pushed major.minor.patch, major.minor, and major tags for appwrite/console-cloud, but this workflow now pushes only the raw release tag. Any production consumer still pinned to the moving 1 or 1.2 aliases will stay on the last image from the old workflow while releases continue deploying a different tag through the declarative repo.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/production.yml
Line: 41

Comment:
**Release Aliases Stop Updating**

The old release job pushed `major.minor.patch`, `major.minor`, and `major` tags for `appwrite/console-cloud`, but this workflow now pushes only the raw release tag. Any production consumer still pinned to the moving `1` or `1.2` aliases will stay on the last image from the old workflow while releases continue deploying a different tag through the declarative repo.

How can I resolve this? If you propose a fix, please make it concise.