ci: sanity check to make sure wasm artifact exists

[dyc3]

Summary

Trying to figure out why our wasm-web package is being published without the wasm.

Test Plan

Docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: e4241c8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

A new verification step has been added to the WASM build workflow in .github/workflows/repository_dispatch.yml. The step runs in the wasm-web package directory and checks for the presence of the biome_wasm_bg.wasm artefact, outputting a confirmation message if found. This verification step is positioned before the existing Publish step.

Possibly related PRs

• ci: fix wasm artifacts again #8470: Modifies WASM artefact handling in CI workflows, including uploads for wasm-web and related components.

Suggested reviewers

• siketyan

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci: sanity check to make sure wasm artifact exists' directly and accurately describes the main change: adding a CI sanity check for the wasm artifact.
Description check	✅ Passed	The description explains the motivation (investigating missing wasm in published package) and is directly related to the changeset's purpose of verifying the wasm artifact exists.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}