feat: create network simulator

[0xmovses]

Changes made

• Created a new simulator crate that will enable us to simulate asynchronous network conditions with more degrees of control. We can use this crate to build out further e2e tests also.

• I had to fork the anr-rs-sdk, as the avalanche-maintained rust client did not support the RPC calls we needed. I made several commits there, updating the rpc.proto file and adding new client methods.

System Deps

NB: These will be managed by the nix dev environment. But for now, when running locally it's critical to have avalanchego installed specifically v.1.10.12.

Pre-reqs

avalanchego binary needs to be in ~/.mvmt/avalanchego/build`, the ANR running in the simulator looks for it at that path. (We can change this path to wherever it will be in the nix shell).

Because the plugin version supported is 28. Any versions higher than this will not work with our vm-plugin subnet. Lower versions are possible, but I went with the latest, working version.

Testing steps

1. create the subnet

cargo build -p subnet --bin subnet
./target/debug/subnet genesis "hello world"
./target/debug/subnet vm-id subnet

1. Run the network-runner

avalanche-network-runner server \
--log-level debug \
--port=":12342" \
--disable-grpc-gateway 

2. Build the simulator cd m1/simulator && cargo build
3. Start the simulator (default nodes amount, 5) cargo run start --verbose, or cargo start --nodes 5
4. cargo add-validator --name node1
5. cargo remove-validator --name node 1
6. cargo add-node --name node6
7. cargo remove-node --name node6

Further Considerations

I ran into an interesting issue to do with avalanchego versions and our vm-plugin version. Our subnet runs vm-plugin version 28 , the latest avalanchego version that can run our subnet is v1.10.12

We have scripts to help with installation, but they have to be run in particular orders, also there are different scripts directories at different places in our workspace. Until we have the nix-shell running with all the deps needed. I could put together a doc for onboarding any devs that are going to be working on the m1 repo, as there are a few system-deps needed and understanding around how we use them, with avalanche-network-runner, for example.

Although, it does seem like nix-shell will be runnable soon, so maybe this doc not needed as that will alleviate all pain points here. I'd say this work around the nix-shell / system- dependencies and dev-ex is separate to the simulator.

[l-monninger]

I'd like to Move this into https://github.com/movementlabsxyz/sdk