fix(cli): strip inline comments when parsing .env values

[amartinawi]

Closes #10100.

loadEnvFile() takes everything after the first =, so KEY=value # note stores the comment text as part of the value. The shipped .env / .env.example do exactly that, so every install runs with:

$ tr '\0' '\n' < /proc/<pid>/environ | grep QUOTA_STORE_DRIVER
QUOTA_STORE_DRIVER=sqlite              # sqlite | redis

$ curl -s -H "authorization: Bearer $KEY" localhost:20128/api/settings/quota-store
{"driver":"sqlite              # sqlite | redis",...}

Why it matters beyond cosmetics

storeFactory.ts compares exactly:

const driver = dbSettings.driver ?? process.env.QUOTA_STORE_DRIVER ?? "sqlite";
if (driver === "redis") { … }

A user who follows the annotation in your own .env.example and writes QUOTA_STORE_DRIVER=redis # sqlite | redis gets driver !== "redis", falls through to SQLite, and sees no warning — the existing QUOTA_STORE_DRIVER=redis but no Redis URL configured warning lives inside the redis branch, so it never fires. Their Redis quota store just never engages. The same trap applies to any variable annotated inline, which the example file encourages.

Change

• New parseEnvValue() with dotenv-compatible semantics: quoted values verbatim (a # inside quotes is data), unquoted values cut at the first whitespace-preceded # — so pass#word and https://host/page#frag survive.
• .env.example moves the annotation to its own line.

Tests

New tests/unit/cli-env-inline-comment-10100.test.ts (5 cases): inline comments stripped, # without preceding whitespace preserved, quoted values verbatim incl. a trailing comment after the closing quote, plain values unchanged, plus a guard asserting .env.example never reintroduces an unquoted inline comment on any variable.

node --import tsx/esm --test tests/unit/cli-env-inline-comment-10100.test.ts  -> 5 pass
npx prettier --check                                                          -> clean