Added RATIFY thresholds

[Soupstraw]

Description

Implemented ratification thresholds. I used a free applicative to assign the fields of PParams into groups. The applicative adds some type safety in ensuring that all the fields are handled while also making it easy to gather all the modified groups in a PParamsUpdate.

closes #3524

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated
• When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
  versioning process.
• The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
• All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
• Code is formatted with fourmolu (use scripts/fourmolize.sh)
• Cabal files are formatted (use scripts/cabal-format.sh)
• hie.yaml has been updated (use scripts/gen-hie.sh)
• Self-reviewed the diff

[lehins]

This is a clever trick with Ap. There is one minor issue with it, which I already mentioned during a meeting that implementation of pparamsGroup depends on the correct order of arguments, but we can solve it at a later point.

Overall looks great. Changes I suggested will be good in order to improve clarity and performance, despite that they slightly diverge from the spec.

[lehins]

Few minor adjustments are still needed, but other than that it looks great. Thank you.