Bump Semgrep to 1.182.1 and allow two unfixable advisories

Semgrep 1.168.0 pins pyjwt~=2.13.0, which dependency-review flags
(GHSA-ffc3-869f-jxw9 and 14 more). Semgrep 1.182.1 requires
pyjwt>=2.15.0; the lock file now has pyjwt 2.15.1, mcp 1.29.0 and
click 8.4.2.

Semgrep 1.182.1 still pins mcp==1.29.0 (GHSA-84m7-p3x7-pcfv) and
opentelemetry-api~=1.37.0 (GHSA-xcq7-p3pf-p88h). Neither code path is
used by `semgrep scan` in CI, so dependency-review allows both until
Semgrep lifts its pins.

Signed-off-by: Niels Lohmann <mail@nlohmann.me>

.github/workflows/dependency-review.yml

@@ -31,3 +31,12 @@ jobs:
           persist-credentials: false
       - name: 'Dependency Review'
         uses: actions/dependency-review-action@a1d282b36b6f3519aa1f3fc636f609c47dddb294 # v5.0.0
+        with:
+          # Semgrep pins mcp==1.29.0 and opentelemetry-api~=1.37.0 exactly
+          # (.github/requirements/semgrep.txt), so these cannot be upgraded
+          # until Semgrep lifts its pins. They do not apply to our use: CI
+          # only runs `semgrep scan` on the checkout and never starts the MCP
+          # server (GHSA-84m7-p3x7-pcfv, StreamableHTTP sessions) or parses
+          # incoming trace context (GHSA-xcq7-p3pf-p88h, tracestate parsing).
+          # Remove the entries once a Semgrep release allows the fixed versions.
+          allow-ghsas: GHSA-84m7-p3x7-pcfv, GHSA-xcq7-p3pf-p88h