chore(deps): bump test-fixture deps + close dependabot coverage gaps (#1188)

* chore(tests): bump hono/fast-uri in fixture lockfiles to clear Dependabot alerts

Ten Dependabot alerts (5 per fixture) flagged fast-uri and hono transitive
deps in tests/echo-rugpull-server and tests/malicious-mcp-server. Both are
local-only npm fixtures for the quarantine/TPA scanner test suite: never
published, never shipped, bound to localhost, spawned only from test
tooling. Real-world exposure is effectively zero; this is alert-noise
hygiene, not a security fix.

Bump fast-uri 3.1.4 -> 3.1.5 and hono 4.12.32 -> 4.12.34 in both
package-lock.json files, keeping the two fixtures on identical versions.
Both are transitive deps of @modelcontextprotocol/sdk (hono) and ajv
(fast-uri) and stay within their existing semver ranges, so package.json
is untouched.

Verified both fixtures still work after the bump: MCP initialize/tools-list/
tools-call round-trips succeed over stdio, and a real mcpproxy instance
connects to both and indexes their tools (echo-rugpull: 2 tools,
malicious: 3 tools).

* chore(ci): close dependabot coverage gaps across npm/docker manifests

.github/dependabot.yml covered gomod:/, github-actions:/, npm:/frontend and
npm:/website only. It never watched tests/echo-rugpull-server or
tests/malicious-mcp-server, which is exactly why ten alerts (5 identical
per fixture, for fast-uri and hono) sat unfixed: nothing was ever going to
open a PR for them. Add both, grouped, with a low open-pull-requests-limit
and a distinct "chore(deps-fixtures)" commit prefix so fixture noise never
crowds out real dependency PRs in review.

Swept the rest of the repo for manifests the config also missed:
- npm: e2e/playwright, e2e/web-ui-sweep — real CI tooling (OAuth E2E,
  web-ui-sweep gate), not fixtures; added like frontend/website.
- npm: bench/tscg — deliberately NOT added. It pins @tscg/core to an exact
  version for discovery-profiler benchmark reproducibility (spec 083);
  auto-bumping would silently invalidate published numbers, same rationale
  as the existing mcp-go ignore rule. Documented inline instead of an
  ignore-only entry that would never produce a PR anyway (zero-dep shim).
- docker: root Dockerfile (the shipped server-edition image) plus the five
  docker/scanners/* wrappers (cisco, proximity, ramparts, snyk, trivy) that
  scanner-images.yml builds and pushes to ghcr.io/smart-mcp-proxy/scanner-*
  — real, shipped, security-relevant base images that had zero Dependabot
  coverage. cmd/mcpfixture is `FROM scratch` and has nothing to track, so
  it's documented as excluded rather than given a no-op entry.
- go.mod: single module at repo root, already covered.

Author: Dumbris

.github/dependabot.yml

@@ -60,3 +60,109 @@ updates:
       website-dependencies:
         patterns:
           - "*"
+  - package-ecosystem: npm
+    directory: "/e2e/playwright"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps)"
+    groups:
+      e2e-playwright-dependencies:
+        patterns:
+          - "*"
+  - package-ecosystem: npm
+    directory: "/e2e/web-ui-sweep"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps)"
+    groups:
+      e2e-web-ui-sweep-dependencies:
+        patterns:
+          - "*"
+  # tests/echo-rugpull-server and tests/malicious-mcp-server are local-only
+  # npm fixtures for the quarantine/TPA scanner test suite (tests/README.md):
+  # never published, never shipped, spawned only from test tooling and bound
+  # to localhost. A vulnerable transitive dep here is alert noise, not a real
+  # exposure — but Dependabot previously had NO entry for either directory,
+  # so ten open alerts (5 per fixture, identical) sat unfixed because nothing
+  # ever opened a PR for them. Low limit + own commit prefix keep fixture
+  # bumps from competing with real dependency PRs for review attention.
+  - package-ecosystem: npm
+    directory: "/tests/echo-rugpull-server"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 3
+    commit-message:
+      prefix: "chore(deps-fixtures)"
+    groups:
+      echo-rugpull-fixture-dependencies:
+        patterns:
+          - "*"
+  - package-ecosystem: npm
+    directory: "/tests/malicious-mcp-server"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 3
+    commit-message:
+      prefix: "chore(deps-fixtures)"
+    groups:
+      malicious-mcp-fixture-dependencies:
+        patterns:
+          - "*"
+  # bench/tscg pins @tscg/core to an exact version (1.4.3) on purpose: the
+  # discovery-profiler benchmark (spec 083) reports figures — e.g. "TSCG
+  # (-23.8%)" in specs/085-compact-router/spec.md — that are only comparable
+  # run-to-run if the shim's encoding behavior doesn't drift. Auto-bumping it
+  # would silently invalidate published numbers, the same reason
+  # github.com/mark3labs/mcp-go is excluded from the gomod group above. No
+  # dependabot entry for bench/tscg; re-pin it manually, in its own reviewed
+  # commit, if a bump is ever warranted.
+  #
+  # cmd/mcpfixture/Dockerfile is `FROM scratch` (see the file's own header
+  # comment) — there is no base image for the docker ecosystem to track, so
+  # it has no entry below either.
+  - package-ecosystem: docker
+    directory: "/"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps)"
+  - package-ecosystem: docker
+    directory: "/docker/scanners/cisco"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps-scanners)"
+  - package-ecosystem: docker
+    directory: "/docker/scanners/proximity"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps-scanners)"
+  - package-ecosystem: docker
+    directory: "/docker/scanners/ramparts"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps-scanners)"
+  - package-ecosystem: docker
+    directory: "/docker/scanners/snyk"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps-scanners)"
+  - package-ecosystem: docker
+    directory: "/docker/scanners/trivy"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "chore(deps-scanners)"