Exclude WASM artifacts from GitHub releases (#23221)

## Summary

Fixes #23127.

The `release.yml` workflow downloads artifacts using `pattern:
artifacts-*` with `merge-multiple: true`. The three WASM build targets
(web, bundler, nodejs) were uploaded as `artifacts-wasm-{target}`,
matching that glob. Since all three
contain identically-named files, they silently overwrote each other
during the
merge, making the released WASM assets non-deterministic.

Renaming the artifacts from `artifacts-wasm-*` to `wasm-npm-*` excludes
them from the `artifacts-*` glob in `release.yml`. Notably, the npm
publish workflow is unaffected (it downloads each target by exact
artifact
name and was never subject to the merge conflict).

## Test Plan

N/A :p

Happy to investigate a test publish on my fork if anyone feels strongly
about this. However, npm does not appear to have a test registry like
PyPI -- and in any event testing seemed a bit involved -- so I didn't
rush to investigate this before review.

---------

Co-authored-by: Brent Westbrook <36778786+ntBre@users.noreply.github.com>

Author: shaanmajid

.github/workflows/build-wasm.yml

@@ -54,5 +54,6 @@ jobs:
       - name: "Upload wasm artifact"
         uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v6.0.0
         with:
-          name: artifacts-wasm-${{ matrix.target }}
+          # Avoid prefixing the name with `artifacts-` here to exclude it from the GitHub release.
+          name: wasm-npm-${{ matrix.target }}
           path: crates/ruff_wasm/pkg

.github/workflows/publish-wasm.yml

@@ -24,7 +24,7 @@ jobs:
     steps:
       - uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7.0.0
         with:
-          name: artifacts-wasm-${{ matrix.target }}
+          name: wasm-npm-${{ matrix.target }}
           path: pkg
       - uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
         with: