CLI WASM Implementation

[gnosed]

• port the CLI rust implementation to WASM

[grarco]

As of commit ac4e32a, the phase1-cli crate can't be compiled to target wasm32 because of a known socket2 issue. More specifically, this dependency is coming from two packages:

• tokio
• hyper

hyper, in turn, comes from:

• reqwest
• hyper-tls (again from reqwest)
• rocket (from phase1-coordinator)

To compile for wasm we can :

• disable the net feature of tokio which is the one pulling in socket2
• remove the rocket dependency coming from phase1-coordinator (related to Refactor repo #12)
• remove std features of reqwest which include hyper-tls (this could be impossible if we plan to use tls)

At this point the only dependency that would need socket2 is the tcp flag of hyper, but this one is disabled when compiling for target wasm32 and so shouldn't cause a problem.

Having done so, we should be able to compile the crate for wasm but we should test whether the removal of features has compromised the runtime functionality in any way

[grarco]

Due to the new issue #27 it may now be impossible to rework the dependencies to successfully compile for a wasm target because of the strong requirement on hyper tcp flag coming from hyper-tls <- reqwest

[grarco]

I'll close this issue. We cannot compile the client to wasm32 unless we remove the communication part with the server that relies on the socket2 crate which is preventing compilation.
That would mean exporting to a different crate the contribute_masp function to be compiled to wasm. After that, we would need to rewrite the entire contribute function from phase1.rs in the frontend and call the wasm compiled contribute_masp function from there