.github/workflows: Migrate workflows to Blacksmith runners

[blacksmith-sh]

This PR has been automatically generated by a team member in your GitHub organization using Blacksmith's Migration Wizard. This PR changes the following:

1. Your selected workflows will now run on Blacksmith's 2x faster hardware (e.g., runs-on: blacksmith-4vcpu-ubuntu-2204). Learn more about the different instances available to choose from.
2. Your jobs running on Blacksmith will now have all official GitHub and popular third-party cache actions automatically interact with our 4x faster, colocated cache. Learn more about Blacksmith's actions cache.
3. Your GitHub Actions will now actually be observable. Learn more about Blacksmith's logging and other observability features.
4. Your Docker builds will now automatically share their Docker layer cache, resulting in up to 40x faster builds. Learn more about Blacksmith's Docker layer caching.

---

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.}

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔍 Matrix jobs only partially migrated to Blacksmith

In the two matrix jobs (integration-tests and run-wfl-programs), only the Windows leg was migrated (windows-latest -> blacksmith-4vcpu-windows-2025) while the Linux leg was left on GitHub-hosted ubuntu-latest (.github/workflows/ci.yml:142 and .github/workflows/ci.yml:294). Every other job in the repo was migrated to blacksmith-4vcpu-ubuntu-2404. This is not a correctness bug — the jobs still run — but the Linux legs of these matrices will not get Blacksmith's faster hardware or colocated cache, so the migration is inconsistent. Worth confirming this partial migration was intentional (e.g. a wizard selection) rather than an oversight.

---

Was this helpful? React with 👍 or 👎 to provide feedback.