Add protobuf module as wasm module

[DmitryAstafyev]

Description

To avoid generating a code for both (rust and JS) sides, we can:

• generate only a rust representation of the protocol.
• create wasm module with generated code
• use wasm module on JS side to decode/encode messages

In this way we can be sure: that messages on rust and JS will be encoded/decoded in the same way

Motivation

Research shows: that using different libraries/modules to generate code based on *.proto at the end can give different results. For example same message can be encoded into different bytes on JS side and on Rust side. That makes work with protocol unpredictable.

[DmitryAstafyev]

General note: code isn't documented at all. It will be before merging.

[AmmarAbouZor]

Wow this a hug and -at the same time- very clean PR 💯

I had a quick look on the rust part and wrote some comments about the point that caught my eyes. Most of them are points for the final phase if the other performance issues are resolved, and some of them could bring tiny improvements for the performance.

[AmmarAbouZor]

I don't know if the backslash will be working on Windows, I think we can test that on Windows first before adjusting it manually. Hopefully the rust compiler can resolve automatically.

[AmmarAbouZor]

I think we can at some point include the use statements inside the macro itself by writing the full paths to the types inside it.
This would make any future changes easier by changing the macro itself and not having to add using statement for each file at a time.