fix(release): set release_ruleset bazel_test_command (avoid //... lazy-dep load) (#511)

The v1.1.1 release_ruleset build job failed: its default `bazel test //...`
can't LOAD examples/moonbit_component (needs @rules_moonbit, deliberately
lazy/not eagerly fetched — rolling-URL checksum drift). Main CI avoids //...
via an explicit allowlist for the same reason.

Override bazel_test_command to build the core rule packages only
(//wasm //wit //rust //go //cpp //js //providers) — a pre-release sanity check;
the full suite already ran in main CI on the tagged commit. Verified locally at
v1.1.1: `bazel build //wasm/... //wit/... //rust/... //go/... //cpp/... //js/...
//providers/...` succeeds (46 targets, no load error).

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: avrabe

.github/workflows/release.yml

@@ -42,6 +42,12 @@ jobs:
       # to the release before it goes live (required for immutable releases).
       draft: true
       tag_name: ${{ inputs.tag || github.ref_name }}
+      # release_ruleset defaults to `bazel test //...`, which fails to LOAD this
+      # repo's optional/lazy-dep example packages (e.g. examples/moonbit_component
+      # needs @rules_moonbit, deliberately not eagerly fetched). Build the core
+      # rule packages only — a pre-release sanity check; the full suite already
+      # ran in main CI on the tagged commit.
+      bazel_test_command: "bazel build //wasm/... //wit/... //rust/... //go/... //cpp/... //js/... //providers/..."
 
   publish:
     needs: release