As these types represent the same value, that is or not encoded with Bech32.

So we can smoothly migrate the Signers first and then the Aggregator on the preview network,
also the Signer certification is not needed in the protocol demo.

To be used on non production usecase such as demo

Errors, add missing 'close' for KeyRegWrapper, and update signature of the 'register' function
so that it can handle smooth implementation with other mithril crates.

That will be used only for tests and by the protocol demo tool which must stay apart from key certification.

That leaded from time to time to interverting the poolId between the pools.

And allow hybrid certification that is enforced only for signers that sign their keys.
This will help a smooth transition with SPOs and avoid service distruption on GCP.
This hybrid mode will be decommissionned in a near future.

Such that half of the signers work with certification and the other half don't.
Also check that all signers are listed in the final certificate tested.

Use auto computation of 'party_id' from operational certificate (if provided)

For tests only

Add a 'Verified Signer' badge for certified signers.

Following update of arguments precedence in #511

To avoid 'warning: very complex type used. Consider factoring parts into  definitions' clippy warning.

The KES Period previously used when registering to Aggregator would have evolved when verified by Signer.
Instead store the KES Period with the other signer material at first.
In a different commit, the KES Period will be enforced within a valid range given an epoch.

And some other enahncements seen during peer reviewing.

This help gracefully handle the operational certificate information returned by cardano cli,
that can be on multiple lines (number of lines may vary).
Now, we scan the output and retrieve the JSON part from the first occurrence of '{'.

And replace its name with 'PartyIdNonExisting'.
Indeed, this error does not belong to the core libray that is Cardano agnostic.

This flag is required for test only functions that are used outside of 'mithril-common'.
It should be activated exclusively on the 'dev-dependencies' configuration block of the crates.

Each type reflects now the native type it encodes.

To decide at a higher level if key certification is enabled.

Replace the 'rust:buster' with 'ubuntu:latest' for building image.
This allows to not rely on libssl1.1 anymore.

Co-authored-by: curiecrypt <[email protected]>

Use 'ubuntu:22.04' instead of 'ubuntu:latest'.