Remove SST runtime integration

[sydneyrenee]

Summary

• remove the SST package, generated ambient files, and SST shell/secret scripts
• replace direct SST resource access with environment-backed resource bindings and worker env bindings
• remove SST-branded docs/examples/social-card endpoints and command arity entries

Verification

• bun typecheck
• git diff --check
• bun test test/cli/github-remote.test.ts (from packages/emberharmony)
• bun --filter @thesolaceproject/emberharmony-console-app build
• bun --filter @thesolaceproject/emberharmony-web build

Notes

• bun install --lockfile-only --ignore-scripts is still blocked by existing fatal OSV advisories for devalue and js-cookie, so the lockfile SST removal was applied directly.
• bun --filter @thesolaceproject/emberharmony-enterprise build still fails in the existing SSR Shiki wasm path: Vite cannot load shiki/dist/onig.wasm without a wasm plugin or ?url/?init handling.

[gemini-code-assist]

Code Review

This pull request removes the dependency on SST (Serverless Stack) across the monorepo, replacing auto-generated SST resources with local environment-variable-based configurations and updating references from SST to EmberHarmony. The code review identified a critical authentication bypass vulnerability in the API's admin secret verification when the environment variable is undefined. Additionally, several medium-severity issues were found in the new environment variable helper functions in drizzle.config.ts and resource.node.ts, where empty strings (such as empty database passwords or ports) are incorrectly treated as falsy, potentially causing configuration failures or defaulting the database port to 0.