[Chore] raise `hedgehog` upper bound

Description

succeeds:

cabal build --constraint 'hedgehog==1.4' --enable-tests

cabal test --constraint 'hedgehog==1.4'

Related issue(s)

closes: https://github.com/serokell/o-clock/issues/142

:white_check_mark: Checklist for your Pull Request

Ideally a PR has all of the checkmarks set.

If something in this list is irrelevant to your PR, you should still set this checkmark indicating that you are sure it is dealt with (be that by irrelevance).

Related changes (conditional)

Tests
- [ ] If I added new functionality, I added tests covering it.
- [ ] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
Documentation
- [x] I checked whether I should update the docs and did so if necessary:
- README
- Haddock
Public contracts
- [x] Any modifications of public contracts comply with the Evolution of Public Contracts policy.
- [x] I added an entry to the changelog if my changes are visible to the users and
- [x] provided a migration guide for breaking changes if possible

Stylistic guide (mandatory)

[ ] My commits comply with the policy used in Serokell.
[x] My code complies with the style guide.

✓ Release Checklist

[ ] I updated the version number in o-clock.cabal.
[ ] I updated the changelog and moved everything under the "Unreleased" section to a new section for this release version.
[ ] If any definitions (functions, type classes, instances, etc) were added, I added @since haddock annotations.
[ ] (After merging) I created a new entry in the releases page, with a summary of all user-facing changes.
- I made sure a tag was created using the format vX.Y.Z
[ ] (After merging) I uploaded the package to hackage.

serokell / o-clock