ci: reduce workflow triggering to cron schedule

[ematipico]

Summary

We decided internally to trigger the dispatch event with a cron job so we don't spend too many resources.

We can still trigger it manually if needed.

Did with an AI agent.

Test Plan

yolo, and merge it

Docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 531cc11

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f87acf6 and 531cc11.

📒 Files selected for processing (1)

• .github/workflows/repository_dispatch.yml

---

Walkthrough

The pull request updates the repository dispatch workflow file, changing the trigger mechanism from push events on main and next branches to a scheduled cron job executing at midnight on Mondays, Wednesdays, and Fridays. The build versioning reference in the WASM step is updated to use github.sha instead of head_commit.id. Repository dispatch steps are consolidated into a single unconditional step, with the payload explicitly including commit SHA and ref values from the workflow context.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: transitioning from push-based triggers to a cron schedule to reduce workflow resource consumption.
Description check	✅ Passed	The description relates to the changeset, explaining the motivation (reducing resource usage) and noting manual triggering remains possible, though the test plan is informal.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/reduce-workflow-dispatch

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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