fix(deploy): launch PM2 via npm to avoid pnpm auto-install crash loop

In a Rush-managed package, pnpm 11's verify-deps-before-run auto-fires a
standalone `pnpm install` before `pnpm run`, which fails with
ERR_PNPM_WORKSPACE_PKG_NOT_FOUND (siblings like @meese-os/eslint-config aren't
present as a pnpm workspace) and crash-loops the service, leaving nothing on
:8000 and producing a Cloudflare 502. npm runs the script without a deps check;
Rush still owns the build in deploy.sh.

Author: ajmeese7

ecosystem.config.js

@@ -10,7 +10,10 @@ module.exports = {
 		{
 			name: "meeseos",
 			script: "/bin/bash",
-			args: ["-c", "pnpm run deploy"],
+			// Launch via `npm`, not `pnpm`: in a Rush package, pnpm's verify-deps-before-run
+			// auto-fires a standalone `pnpm install` that fails (ERR_PNPM_WORKSPACE_PKG_NOT_FOUND)
+			// and crash-loops the service. npm just runs the script. Build is handled by deploy.sh.
+			args: ["-c", "npm run deploy"],
 			cwd: websiteDir,
 			instances: 1,
 			exec_mode: "fork",