Classify non-Node app types (python/go/docker/static) in streamingDetect

[atomantic]

`streamingDetect.js` emits `vite+express` / `vite` / `single-node-server` / `nextjs`, the four Apple types, or `unknown` (the initialized default) — there is no `python`, `go`, `docker`, or `static`. `usesPm2()` is the negation of `NON_PM2_TYPES` (the four Apple types), so everything unrecognized is treated as a PM2 app: a Python service, Docker stack, Go binary, or static site all come back `unknown` and are still offered PM2 standardization in the Add App wizard. That matters because the standardizer's prompt opens with "You are analyzing a Node.js application" (`server/services/pm2Standardizer.js`) — on a Python repo it doesn't fail, it confidently writes a Node ecosystem config. The auto-fire is gone (standardizing is now an explicit button whose copy says "skip it for Docker stacks, static sites, or anything you start another way"), so this is no longer a data-loss path, but the prose is doing a type check's job.

Fix shape: don't widen `NON_PM2_TYPES` — its three other consumers mean "Apple", not "not PM2". Teach `streamingDetect` to classify `python` / `go` / `docker` / `static` from marker files (`pyproject.toml`/`requirements.txt`, `go.mod`, `docker-compose.yml` with no package.json, `index.html` with no server) so `unknown` stops being the catch-all, then add a positive `isStandardizable(type)` predicate over the Node types and gate both the wizard card and `standardizeRefusalFor()` on it. Note `type` is persisted on the app record, so an existing `unknown` app keeps that type until re-detected — the predicate must stay permissive for `unknown` or offer a re-detect.

Surfaced by the /simplify altitude review on the opt-in-standardization change.

Migrated from PLAN.md by /do:replan --issues.

[atomantic]

Implemented in #4233. Decisions made while claiming this (unattended run):

• Followed the issue's guidance and did not widen NON_PM2_TYPES — usesPm2() still returns true for the new types, since a Python or Go service genuinely runs under PM2.
• The new gate is a deny list (NON_STANDARDIZABLE_TYPES = NON_PM2_TYPES ∪ NON_NODE_TYPES) rather than an allowlist of Node types. type is a free-form string persisted on the app record (appSchema defaults it to express and accepts any value), so records in the wild carry values detection never emitted; an allowlist would silently withdraw the standardize button from all of them on upgrade. This generalizes the issue's "the predicate must stay permissive for unknown" requirement instead of special-casing it.
• Classification order is language → Node server entry → docker → static, so a containerized Python service is python, a package-less repo shipping server.{js,mjs,cjs,ts} or an ecosystem.config.* stays standardizable, and static keeps the issue's "index.html with no server" condition. Only server counts as a server basename — index.js/app.js/main.js are at least as common as browser scripts.
• Also closed an adjacent gap the new gate exposed: resolveStandardizeTarget in server/routes/standardize.js preferred a companion repoPath over the app.repoPath it had just type-checked, so a permitted Node appId paired with another directory could carry a non-Node repo past the refusal.