chore(quality): prune stale eslint-suppressions entries

Two entries no longer match current violation counts (open-sse/executors/index.ts
from the #11421 lazy-executor refactor, open-sse/services/autoCombo/routerStrategy.ts
from the #11555 docs cleanup), both already merged. Left stale, the suppression
mechanism's all-or-nothing count-mismatch behavior surfaces every other file's
suppressed violations as apparent errors on any lint run, which is why the same
~228 dashboard react-hooks/* findings kept appearing as "pre-existing, unrelated"
in unrelated PRs merged today. Note (separate infra issue): the shared main
checkout's node_modules/eslint-config-next is itself missing its dist/ files
(package.json only) -- a fresh npm install resolves it and this prune is
still correct once that install happens.

config/quality/eslint-suppressions.json

@@ -159,11 +159,6 @@
       "count": 1
     }
   },
-  "open-sse/executors/index.ts": {
-    "@typescript-eslint/no-unused-vars": {
-      "count": 1
-    }
-  },
   "open-sse/executors/kiro.ts": {
     "@typescript-eslint/no-unused-vars": {
       "count": 3
@@ -476,11 +471,6 @@
       "count": 2
     }
   },
-  "open-sse/services/autoCombo/routerStrategy.ts": {
-    "@typescript-eslint/no-unused-vars": {
-      "count": 2
-    }
-  },
   "open-sse/services/bailianQuotaFetcher.ts": {
     "no-restricted-syntax": {
       "count": 1