Add CLI interface for verifier contract generation

[CPerezz]

This PR adds a new crate to the workspace which is a CLI interface that allows to create Solidity smart contracts which verify paritcular protocols.

It doesn't only include the CLI but also tools to serialize all the data required to be used by the CLI in a simple manner.

This is how the CLI --help command actually looks like:

 _____  ______  ______  ______  ______  ______  ______ 
| |__| || |__| || |__| || |__| || |__| || |__| || |__| |
|  ()  ||  ()  ||  ()  ||  ()  ||  ()  ||  ()  ||  ()  |
|______||______||______||______||______||______||______|
 ______                                          ______ 
| |__| |   ____        _ _     _ _ _            | |__| |
|  ()  |  / ___|  ___ | (_) __| (_) |_ _   _    |  ()  |
|______|  \___ \ / _ \| | |/ _` | | __| | | |   |______|
 ______    ___) | (_) | | | (_| | | |_| |_| |    ______ 
| |__| |  |____/ \___/|_|_|\__,_|_|\__|\__, |   | |__| |
|  ()  |  __     __        _  __ _     |___/    |  ()  |
|______|  \ \   / /__ _ __(_)/ _(_) ___ _ __    |______|
 ______    \ \ / / _ \ '__| | |_| |/ _ \ '__|    ______ 
| |__| |    \ V /  __/ |  | |  _| |  __/ |      | |__| |
|  ()  |     \_/ \___|_|  |_|_| |_|\___|_|      |  ()  |
|______|                                        |______|
 ______  ______  ______  ______  ______  ______  ______ 
| |__| || |__| || |__| || |__| || |__| || |__| || |__| |
|  ()  ||  ()  ||  ()  ||  ()  ||  ()  ||  ()  ||  ()  |
|______||______||______||______||______||______||______|

Welcome to Solidity Verifier, a powerful Command-Line Interface (CLI) tool designed to simplify the generation of Solidity smart contracts that verify proofs of Zero Knowledge cryptographic protocols.
for Zero Knowledge protocols. This tool is developed by the collaborative efforts of the PSE (Privacy & Scaling Explorations) and 0XPARC teams. 

As an open-source project, Solidity Verifier is released under the GPL3 license.

Solidity Verifier currently supports the generation of Solidity smart contracts for the verification of proofs in the following Zero Knowledge protocols:

    Groth16:
        Efficient and succinct zero-knowledge proof system.

    KZG:
        Uses the Kate-Zaverucha-Goldberg polynomial commitment scheme.

    Nova + CycleFold Decider:
        Implements the decider circuit verification for the Nova zero-knowledge proof system in conjunction with the CycleFold protocol optimization.


Usage: solidity-verifier [OPTIONS] --protocol <PROTOCOL> --protocol-data <PROTOCOL_DATA>

Options:
  -v, --verbose...
          Increase logging verbosity

  -q, --quiet...
          Decrease logging verbosity

  -p, --protocol <PROTOCOL>
          Selects the protocol for which we want to generate the Solidity Verifier contract
          
          [possible values: groth16, kzg, nova-cyclefold]

  -o, --out <OUT>
          Sets the output path for all the artifacts generated by the command
          
          [default: /PATH-TO/verifier.sol]

  -d, --protocol-data <PROTOCOL_DATA>
          Sets the input path for the file containing all the data required by the protocol chosen such that the verification contract can be generated

      --pragma <PRAGMA>
          Selects the Solidity compiler version to be set in the Solidity Verifier contract artifact

  -h, --help
          Print help (see a summary with '-h')

  -V, --version
          Print version

[CPerezz]

After this, I just need to bring back the assets to test the three different supported protocols, add logging and cleanup.

So far, this is what calling solidity-verifier --help looks like:

**A tool to create Solidity Contracts which act as verifiers for the major Folding Schemes implemented within the `folding-schemes` repo

Usage: solidity-verifier [OPTIONS] --protocol <PROTOCOL> --protocol-data <PROTOCOL_DATA>

Options:
  -v, --verbose...                     Increase logging verbosity
  -q, --quiet...                       Decrease logging verbosity
  -p, --protocol <PROTOCOL>            Selects the protocol for which we want to generate the Decider circuit Solidity Verifier [possible values: groth16, kzg, nova-cyclefold]
  -o, --out <OUT>                      Sets the output path for all the artifacts generated by the command [default: /path/to/the/place/where/we_want/verifier.sol]
  -d, --protocol-data <PROTOCOL_DATA>  Sets the input path for the file containing all the data required by the protocol chosen such that the verification contract can be generated
      --pragma <PRAGMA>                Selects the Solidity compiler version to be set in the Solidity Verifier contract artifact
  -h, --help                           Print help
  -V, --version                        Print version

Aside from that. We should be close to close this. It took me some time to figure out a way to don't need Protocol definitions in both crates but seems difficult to avoid unless I want to have a cli feature in folding-schemes-solidity where I also derive ValueEnum for Protocol enum there. In this way, I can reduce even further the duplication.

I also tried an aproach where I had clap::SubCommand for each protocol. Thus having it's required parameters inside each of the subcommand enum definitions.
While easier to impl that this, it requires the user to pass like 3 or 4 paths/files to the command for NovaCycleFold which is absurd.

With the ProtocolData approach instead, the CLI interface is significantly simpler and also much easier to handle the data associated to each protocol.

[CPerezz]

Will fix the asset deserialization issues in the tests tomorrow. And after that. I think we're good to go!

[dmpierre]

lgtm! thanks for this Carlos. Added a few suggestions and questions here and there.

[arnaucube]

Great work! Left few suggestions

[arnaucube]

LGTM! 🚀