refactor: deploy Community with shared Cloudflare platform

[KingDoxik]

Summary

• move reusable Cloudflare and Node platform adapters into packages/platform
• deploy the Community backend and web application through an Alchemy-managed Cloudflare stack
• configure Cloudflare credentials, custom domains, and workers.dev exposure through .env
• retain the Node platform as an optional portability and integration-test package
• remove the former self-host deployment composition and relocate its Node fixtures

Why

Community deployment should use provider-neutral application seams and one Alchemy development workflow. A distinct VoidhashCommunity stack namespace allows the composition to coexist with other Alchemy stacks in one Cloudflare account.

Impact

Operators can configure PostgreSQL, Cloudflare credentials, backend and web domains, and runtime secrets in .env, then deploy with pnpm alchemy deploy --stage production. Custom-domain configuration also supplies the default public backend origin.

Validation

• pnpm check:publication
• pnpm check:platform-seam
• backend and web application TypeScript checks
• targeted formatting and lint checks for the deployment composition
• read-only Alchemy live plan with custom domains and workers.dev disabled

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[greptile-apps]

Too many files changed for review (108 files, 100 file limit).

Bypass the limit by tagging @greptile-apps to review.

[github-actions]

Install the packages built from d4f9f02:

@voidhash/paywalls

pnpm add @voidhash/paywalls@https://pkg.voidha.sh/paywalls/d4f9f02

@voidhash/node

pnpm add @voidhash/node@https://pkg.voidha.sh/node/d4f9f02

@voidhash/web

pnpm add @voidhash/web@https://pkg.voidha.sh/web/d4f9f02

voidhash-cli

pnpm add voidhash-cli@https://pkg.voidha.sh/cli/d4f9f02

@voidhash/react-native

pnpm add @voidhash/react-native@https://pkg.voidha.sh/react-native/d4f9f02

Internal workspace deps (lib, generated-clients, shared, studio) are published at the same sha and resolved automatically.

Replace the sha with pr-126 or the branch name to always get the latest build of this PR.