Improve pre commit hook: make it block hlint issues

[smelc]

Changelog

- description: |
    Update to the pre-commit script, so that it fails on hlint errors
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

Fixes #294

How to trust this PR

1. Try the procedure described in Pre-commit hook doesn't fail on hlint failure #294.
2. Witness that the git commit -m "try commit" step now fails

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• The change log section in the PR description has been filled in
• NA New tests are added if needed and existing tests are updated. These may include:
  • golden tests
  • property tests
  • round trip tests
  • integration tests
    See Running tests for more details
• NA The version bounds in .cabal files are updated
• CI passes. See note on CI. The following CI checks are required:
  • Code is linted with hlint. See .github/workflows/check-hlint.yml to get the hlint version
  • Code is formatted with stylish-haskell. See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
  • Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7
• NA The changelog section in the PR is updated to describe the change
• Self-reviewed the diff

[carbolymer]

Awesome! Thanks. We have the same hook in the same place in cardano-node and cardano-api also. Can you migrate the changes there as well?

[smelc]

Awesome! Thanks. We have the same hook in the same place in cardano-node and cardano-api also. Can you migrate the changes there as well?

@carbolymer> on my way 👍