Added SPO voting thresholds for security relevant parameters

[Soupstraw]

Description

This PR adds a way to mark protocol parameter fields as SecurityRelevant. The security relevant fields require sufficient votes from SPOs, where the required votes are determined by the pvtSecurityRelevant parameter.

resolves #3925

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]

Logic looks great. I am not too fond of some naming choices, but that should be easy to fix.

[lehins]

I've discussed this with @WhatisRT and current behavior implemented in this PR is indeed the desired behavior.

Great work!