[WIP] Integrate Peras voting committee into BlockSupportsPeras

[agustinmista]

Description

Please include a meaningful description of the PR and link the relevant issues
this PR might resolve.

Also note that:

• New code should be properly tested (even if it does not add new features).
• The fix for a regression should include a test that reproduces said regression.

WARNING

To update your feature branch if it's stale, please rebase it manually on top of main. Don't update your feature branch by merging main into it. Your pull request will not pass CI if you do.

[tbagrel1]

Next steps:

• Merge PerasVoteStake and VoteWeight (and eliminate the current coerce in implForgePerasVoteIfElligible
• Make sure eligiblePartyVoteWeight returns a normalized VoteWeight and add corresponding docstring
• Merge (Peras)SeatIndex and PerasVoterId
• Unify VotesReachingQuorum and UniqueVotesWithSameTarget
• Write blk-generic instances for implForgePerasCert, implVerifyPerasVote, implVerifyPerasCert as we did for implForgePerasVoteIfElligible
• Modify the interface for forgePerasCert, verifyPerasVote, verifyPerasCert and adapt calling code (this should make PerasVoteStakeDistr useless, and we should be able to remove)
• Make forgePerasVoteIfElligible part of BlockSupportsPeras
• Include the new type families and corresponding superclass constraints as part of BlockSupportsPeras
• Remove instance of BlockSupportPeras for RealBlock from Praos/Peras.hs and instead use the code to provide concrete instances for ShelleyBlock proto DijkstraEra and HardForkBlock xs
• Move getStakeDistrWithBLSPublicKeys and perasBLSPublicKeysFromEnv out of Praos/Peras.hs
• Introduce IsPerasError class to gather the injectXXXError :: XXX -> PerasError blk functions and instance it
• Add committee target size as part of PerasParams and use it in praosStatePerasVotingCommitteeInput. Also (re)-export the dedicated type from PerasParams

[tbagrel1]

Future steps for another PR:

• Have some machinery getCommitteeForRound :: PerasRoundNo -> Maybe (PerasVotingCommittee blk), which involves running Qry/Summary and doing epoch dispatch for the committee (so far it can be simple: just check the supplied PerasRoundNo corresponds to the current epoch, and return the current committee from Praos state)
• Decide if we want components to interact with getCommitteeForRound and feed the obtained committee into BlockSupportsPeras method, or if we want another layer of abstraction laying near PraosState that would do the resolution for them (exposing methods similar to BlockSupportsPeras, but where the Committee argument is no longer there, and either replaced with PraosState, or capturing a handle to PraosState so dispatch can happen transparently)