claude:chore: broaden vite scripts' NODE_OPTIONS to --no-warnings

A second Node warning appeared on `yarn dev`:

  UnsupportedWarning: Status message is not supported by HTTP/2
  (RFC7540 8.1.2.4)

This fires when a middleware reflexively sets `statusMessage` on
an HTTP/2 response (HTTP/2 has no status messages per RFC 7540
§8.1.2.4); the browser negotiates HTTP/2 over the basic-ssl HTTPS
the dev server hands out. Like DEP0169, the warning is informational
and doesn't affect behaviour.

`--no-deprecation` only filters Deprecation warnings, not
UnsupportedWarnings. Switching to `--no-warnings` covers both
(deprecation is a subset of warnings), so the dev/build/preview
output stays clean against any current or future Node warning class.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: kuco23

package.json

@@ -6,11 +6,11 @@
   "packageManager": "yarn@1.22.22",
   "homepage": "stakecore.org",
   "scripts": {
-    "dev": "NODE_OPTIONS=--no-deprecation vite",
-    "build": "NODE_OPTIONS=--no-deprecation vite build",
+    "dev": "NODE_OPTIONS=--no-warnings vite",
+    "build": "NODE_OPTIONS=--no-warnings vite build",
     "clean": "vite clean",
     "lint": "eslint .",
-    "preview": "NODE_OPTIONS=--no-deprecation vite preview",
+    "preview": "NODE_OPTIONS=--no-warnings vite preview",
     "----------- openapi -----------------------": "",
     "openapi-fix": "sed -i \"s|BASE: *'',|BASE: 'https://backend.stakecore.org',|\" ./src/backendApi/core/OpenAPI.ts",
     "openapi-gen": "yarn openapi -i ./openapi.json -o ./src/backendApi && yarn openapi-fix",