Crypto: bootstrap signature v2

What

This MR introduce a new version of the Signature module.

Why

For the AQEAB project, we need to change internal way of handling BLS signature and also need to add some function for this algorithm.

How

By introducing Signature.V2 module base on !6302 (merged) . Introducing this new version breaks a lot of things. Protocol since Mumbai use the version 1, with the new version, V_latest has move from 1 to 2. Even if Signature version is well handled in the tezos protocols, in a lot of Octez places (baker, client, dal, sc_rollup_node, tests, etc) the call for Signature functions were hardcoded with the full path Tezos_crypto.Signature. and this path is equivalent to Tezos_crypto.Signature.V_latest. That mean that we need to explicit the fact that for all octez protocol related piece of code the Signature module is the version 1.

Another point is that the octez lib by default use the latest version but that is not the case anymore for proto related code. Some "cast" needs to be done when Signature related value or used from octez lib in proto related code.

Manually testing the MR

Typing MR, Green CI should be good.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR