higress: leave USE_PLUGIN_SERVER at its shipped default; add star snapshot

Drop the env override USE_PLUGIN_SERVER=off and the matching why claim. The bench
measures the artifact as it ships (minimal config, out-of-the-box), and the plugin
server is a default-on process in the same way the console JVM is - which this manifest
deliberately keeps in the RSS. Turning it off would shave measured memory below the
image's real footprint, inconsistent with keeping the JVM. Also record higress in the
committed GitHub star snapshot (9,195, alibaba/higress).

Author: MattJackson

gateways/higress/env

@@ -4,4 +4,3 @@
 # gateway's OWN knob (not one of the runtime-standard names the harness sets centrally for every
 # entrant), so it is declared here, from {NCORE}, exactly once.
 GATEWAY_CONCURRENCY={NCORE}
-USE_PLUGIN_SERVER=off

gateways/higress/why

@@ -19,19 +19,6 @@ env GATEWAY_CONCURRENCY={NCORE}
   like GOMAXPROCS centrally), so it is declared per-gateway, from {NCORE}, exactly as the manifest
   spec's one exception allows.
 
-env USE_PLUGIN_SERVER=off
-  measure. The all-in-one image defaults this to on, which keeps the built-in plugin server - a
-  resident nginx listening on 8002 inside the container - serving Wasm plugin images to Envoy over
-  local HTTP; base.sh normalizes off/false/no to off, and with it off start-plugin-server.sh exits
-  at boot. This manifest configures no Wasm plugin anywhere - no WasmPlugin resource, no plugin
-  annotation on the Ingress, and the McpBridge is used purely as a static registry - so that nginx
-  can never answer a request, and the project's own deploy-by-docker table says the alternative
-  source it enables (the public image server) is only consulted when a Wasm plugin must be
-  fetched, which nothing here ever does. This is the manifest's one turn-off of a default-on
-  component, made on the same minimality principle the rest of the config lives by: the process
-  exists to serve a capability this deployment does not configure, and leaving it on would count
-  an idle nginx's RSS in figures that already honestly carry the console JVM's.
-
 mount data/mcpbridges/default.gen.yaml -> /data/mcpbridges/default.yaml (read-only)
   upstream. The all-in-one bootstrap (start-apiserver.sh) copies its defaults into /data with
   cp -n, so an existing file at this path survives and ours - pointing the sole static registry at

gateways/stars.json

@@ -19,13 +19,13 @@
   "first_commit": "2025-03-19",
   "as_of": "2026-08-26"
  },
- "busbar-151": {
+ "busbar": {
   "stars": 116,
   "first_commit": "2026-05-29",
   "as_of": "2026-08-26"
  },
  "gomodel": {
-  "stars": 1082,
+  "stars": 1083,
   "first_commit": "2025-12-13",
   "as_of": "2026-08-26"
  },
@@ -34,6 +34,11 @@
   "first_commit": "2025-04-01",
   "as_of": "2026-08-26"
  },
+ "higress": {
+  "stars": 9195,
+  "first_commit": "2022-10-27",
+  "as_of": "2026-08-26"
+ },
  "kong": {
   "stars": 44043,
   "first_commit": "2014-11-17",