Deprecate Appwrite Docs MCP server

[ChiragAgg5k]

Summary

• remove the staging deployment workflow
• mark the Appwrite Docs MCP server as deprecated
• direct users to migrate to appwrite/mcp

Testing

• git diff --check
• not run (documentation and workflow removal only)

[greptile-apps]

Greptile Summary

This PR deprecates the Appwrite Docs MCP server by adding a prominent warning callout to the README and removing the staging deployment workflow. The production deployment workflow is intentionally kept active so existing users continue to be served during the migration window.

• README.md: A [!WARNING] GitHub callout is inserted immediately after the page title, directing users to migrate to appwrite/mcp before the server is sunset.
• .github/workflows/staging.yml: The staging CI/CD pipeline is removed entirely; .github/workflows/production.yml remains in place.

Confidence Score: 5/5

Safe to merge — changes are limited to documentation and workflow removal with no impact on application logic.

Both changes are intentional and well-scoped: the README gets a clear deprecation callout pointing users to the replacement, and the staging workflow is removed. The production workflow is deliberately left in place so the server stays reachable during the wind-down period. No code is modified.

No files require special attention.

Important Files Changed

Filename	Overview
README.md	Adds a GitHub-flavored [!WARNING] callout at the top directing users to migrate to appwrite/mcp; also removes trailing blank lines at the end of the file.
.github/workflows/staging.yml	Entire staging deployment workflow deleted; the production workflow (production.yml) is intentionally retained to keep the server available during the deprecation window.

_{Reviews (1): Last reviewed commit: "chore: deprecate docs MCP server" | Re-trigger Greptile}