Drop the Deno target

The deno step mapped every package to https://deno.land/x/pezkuwi/..., which
never existed (nor does @pezkuwi on JSR): it was red on every run, hidden by
continue-on-error. Decided 2026-10-07: no Deno build. The src/mod.ts entry
points (imported by nothing else, and the switch that makes the build emit
build-deno/), the import maps, the deno script and the CI step are removed.
The npm packages are unchanged; Deno users can import them as npm:.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

.github/workflows/pr-any.yml

@@ -6,7 +6,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        step: ['lint', 'test', 'build', 'deno']
+        step: ['lint', 'test', 'build']
     runs-on: ubuntu-latest
     env:
       YARN_ENABLE_SCRIPTS: false
@@ -16,14 +16,9 @@ jobs:
     - uses: actions/setup-node@v4
       with:
         node-version: 'lts/*'
-    - uses: denoland/setup-deno@v1
-      with:
-        # Deno v2 throws errors with specific types therefore we set it to the last version before v2
-        deno-version: v1.46.3
     - name: ${{ matrix.step }}
       if: always()
       run: |
-        deno --version
         yarn install --immutable
         yarn ${{ matrix.step }}
     # The package.json each build/ directory holds is what npm receives: every