Use mise to manage ormolu and cabal-gild in CI and locally

[cprecioso]

Description

• Related Use pre-built dev tools for our local environments #3927

Important

For an overview of what is Mise, how it works and how it (doesn't) change our local environments, I made this small write-up: https://gist.github.com/cprecioso/a5cdae82d31dfe3561c7db1c49df594c

Introduce mise as the version manager for formatting tools (ormolu and cabal-gild), replacing the previous approach of building them from source via dev-tool.project and using third-party GitHub Actions. This gives a single source of truth for tool versions (mise.toml), faster CI runs (pre-built binaries instead of Cabal builds), and a simpler local developer experience (run through mise instead of install_dev_tool/dev_tool_path).

Changes:

• Add mise.toml and mise.lock at the repo root pinning ormolu and cabal-gild versions.
• Update waspc/run to invoke tools via mise x instead of building them from dev-tool.project.
• Remove ormolu and cabal-gild version constraints from dev-tool.project.
• Replace haskell-actions/run-ormolu and tfausak/cabal-gild-setup-action in CI with jdx/mise-action.

This unlocks upgrading the versions of ormolu and cabal-gild:

• Upgrade ormolu from 0.7.2.0 to 0.8.0.2 #3931
• Upgrade cabal-gild from 1.5.0.1 to 1.7.0.2 #3932

Type of change

• 🔧 Just code/docs improvement
• 🐞 Bug fix
• 🚀 New/improved feature
• 💥 Breaking change

Checklist

• I tested my change in a Wasp app to verify that it works as intended.

• 🧪 Tests and apps:

  • I added unit tests for my change.
  • (if you fixed a bug) I added a regression test for the bug I fixed.
  • (if you added/updated a feature) I added/updated e2e tests in examples/kitchen-sink/e2e-tests.
  • (if you added/updated a feature) I updated the starter templates in waspc/data/Cli/templates, as needed.
  • (if you added/updated a feature) I updated the example apps in examples/, as needed.
    • (if you updated examples/tutorials) I updated the tutorial in the docs (and vice versa).

• 📜 Documentation:

  • (if you added/updated a feature) I added/updated the documentation in web/docs/.

• 🆕 Changelog: (if change is more than just code/docs improvement)

  • I updated waspc/ChangeLog.md with a user-friendly description of the change.
  • (if you did a breaking change) I added a step to the current migration guide in web/docs/migration-guides/.
  • I bumped the version in waspc/waspc.cabal to reflect the changes I introduced.

[cprecioso]

mise x ormolu ensures that we're using the Mise-requested ormolu version even if Mise is not correctly hooking into the current env, or if the tool is not yet installed.

[pkg-pr-new]

Open in StackBlitz

@wasp.sh/wasp-cli

npx https://pkg.pr.new/@wasp.sh/wasp-cli@3930

@wasp.sh/wasp-cli-darwin-arm64-unknown

npx https://pkg.pr.new/@wasp.sh/wasp-cli-darwin-arm64-unknown@3930

@wasp.sh/wasp-cli-darwin-x64-unknown

npx https://pkg.pr.new/@wasp.sh/wasp-cli-darwin-x64-unknown@3930

@wasp.sh/wasp-cli-linux-x64-glibc

npx https://pkg.pr.new/@wasp.sh/wasp-cli-linux-x64-glibc@3930

@wasp.sh/wasp-cli-linux-x64-musl

npx https://pkg.pr.new/@wasp.sh/wasp-cli-linux-x64-musl@3930

commit: a532f2f