chore(deploy): push image bumps to application-configuration

[levivannoort]

What

mcp moved out of assets-applications into application-configuration (appwrite-labs/application-configuration#12), which is laid out as <project>/<env>/<app> instead of <env>/<app>.

Affected workflows: production,staging.

-  PROJECT: mcp
+  PROJECT: assets
+  APPLICATION: mcp
-  DECLARATIVE_REPOSITORY: assets-applications
+  DECLARATIVE_REPOSITORY: application-configuration

-  ${{ env.ENVIRONMENT }}/${{ env.PROJECT }}/default.yaml
+  ${{ env.PROJECT }}/${{ env.ENVIRONMENT }}/${{ env.APPLICATION }}/default.yaml

PROJECT now names the project and APPLICATION the app, matching the dns workflows already deploying to that repo. The commit subject still names the app, so the bump commits read the same as before.

The declarative-deployment GitHub App is already installed on application-configuration — it is what the dns pipeline authenticates with.

Merge order

Last. ArgoCD has to be reading the new repo first, otherwise a bump lands where nothing syncs from. Order: appwrite-labs/reusable-workflows#10 → appwrite-labs/application-configuration#12 → appwrite-labs/cluster-configuration-generator#158 (plus its generated PR into cluster-configuration) → this.

[greptile-apps]

Greptile Summary

The PR redirects production and staging image-tag bumps from assets-applications to the new application-configuration hierarchy.

• Separates the assets project name from the mcp application name.
• Updates manifest paths to assets/<environment>/mcp/default.yaml.
• Preserves mcp in generated bump commit subjects.

Confidence Score: 5/5

The PR appears safe to merge after the prerequisite repository and ArgoCD migrations described in the required merge order.

Both workflows consistently scope authentication and checkout to the new repository, update and stage the same destination manifest, and retain the application name in bump commits; no actionable changed-code failure remains.

Important Files Changed

Filename	Overview
.github/workflows/production.yml	Updates the production deployment destination, manifest path, and commit subject consistently with the new repository layout.
.github/workflows/staging.yml	Applies the same internally consistent repository and path migration to staging.

_{Reviews (1): Last reviewed commit: "chore(deploy): push image bumps to appli..." | Re-trigger Greptile}