fix(site): ship React with the server so the image starts

[devchaudhary24k]

What broke

v0.2.0 deployed, but the Site's new container never replaced the old one, so commitscape.damnlabs.com kept serving 0.1.1.

The v0.2.0 Site image answers every request, /api/health included, with a 500:

Error: Cannot find module 'react'
  at file:///app/.output/server/_ssr/cards-….mjs

Recharts, new in 0.2.0, reaches React through react-redux → use-sync-external-store, which loads it with require("react"). The bundle leaves that require to run at run time. In the repo and in CI's e2e there is a node_modules beside the output, so it resolves; the image has only /app/.output, so it fails. The health check never passes and Dokploy keeps the previous container.

The fix

• apps/site/vite.config.ts: Nitro now traces react and react-dom into .output/server/node_modules, so the require finds them and every part of the Site uses that one copy.
• apps/site/e2e/foundation.spec.ts: the repository page test pressed Ctrl+K before the page listened for it, which failed CI on main for the 0.2.0 commit. It now presses again until the palette is shown.

Checked

• Built the Site Docker image from this branch and ran it: home, profile, Cards, Work, Standing, repository, Leaderboards, Versus, Races, Crews, Privacy, and Card SVG and PNG all answer 200, the log has no errors, and Docker reports it healthy.
• The published v0.2.0 image, run the same way, answers 500 on /api/health and never becomes healthy.
• The v0.2.0 Builder image starts and works; only the Site was affected.
• pnpm check passes. The Card PNG timing test went over its 200 ms limit once on a loaded machine and passed on its own (33 of 33).
• pnpm e2e: 58 of 58. The fixed test passed 8 of 8 when repeated.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}