ci: add reusable advance-deploy-env workflow

[LukasWodka]

Summary

Adds a reusable workflow at .github/workflows/advance-deploy-env.yml that each active repo will call on push to develop, staging, master, or main. For every PR contained in the push, it updates the PR's project card:

• develop merge → Deploy environment = dev
• staging merge → Deploy environment = staging
• master/main merge → Deploy environment = prodandStatus = Done

This implements the "Done = shipped to prod" model from the kanban redesign — Status sits in Validation while a PR is on dev/staging, and only flips to Done when production-merged.

Why a reusable workflow

Same pattern as the kanban auto-add: write the logic once, call it from each repo with a 5-line caller. No duplication, easy to update.

Dependencies

• Org secret PROJECTS_KANBAN_TOKEN (already configured)
• Project fields Deploy environment and Status on engineer kanban (already created)

Activation

This PR alone does not change anything — the file is dormant until each repo opts in by adding a thin caller workflow. Caller rollout will be a follow-up batch of PRs.

Test plan

• After merge: any push to a non-target branch (e.g. chore/foo) is a no-op (workflow logic checks ref_name)
• Once one caller is wired up: merge a small PR to develop, verify the PR's Deploy environment field flips to dev on the project board
• Same flow on master/main merge: verify Status flips to Done and Deploy environment flips to prod

🤖 Generated with Claude Code