Tracking: Migration of select submodules from snarkOS into snarkVM

[howardwu]

In an effort to formalize Aleo records (for usability), reduce miner code dependencies (for security), and introduce an abstraction layer for DPC (for modularity), we are migrating select submodules from snarkOS into snarkVM.

• algorithms
• benchmarks
• curves
• dpc
• gadgets

This migration will allow snarkVM to focus on its core functionality of facilitating predicate (application) executions, producing DPC records, and composing records into transactions. This migration will also simplify the existing dependency chain for a number of repositories currently upstream. In addition, this migration should improve snarkOS compile times significantly.

In preparation for this migration, there are a few updates snarkOS will need to make in order to ensure a smooth transition.

• Remove Storage trait implementations #139 - Remove Storage trait implementations
• Remove parameters from snarkos-dpc #140 - Remove parameters from snarkos-dpc

To complete this migration, 3 submodules in snarkOS will need a minor update, calling components from snarkVM now.

In snarkos-consensus:

• dpc - InstantiatedDPC will be called from snarkVM
• dpc - PublicParameters will be called from snarkVM

In snarkos-network:

• dpc - Instantiated components of DPC will be called from snarkVM
• dpc - InstantiatedDPC will be called from snarkVM
• dpc - PublicParameters will be called from snarkVM

In snarkos-posw:

• gadgets - Merkle gadget will be called from snarkVM
• curves - BLS12-377 will be called from snarkVM

Lastly, prior to publishing snarkVM to Crates.io, to ensure Travis CI continues to run, a private dependency link will be used for continuous integration.

[gakonst]

What is the latest on this? IIUC we're not moving forward with the OS->VM migration