fix(networking): Switch to ggrs fork with fix for corrections dropped…

… at max prediction (#382)

Switching to fork of ggrs with some fixes I am testing for desync.
Desync occurs when client receives a frame it should rollback and
correct while also at max prediction threshold (requires 3+ clients to
hit failure, as if only 2 after receiving remote input 2nd would not be
at max prediction anymore).

Changes being used are here:
https://github.com/MaxCWhitehead/ggrs/tree/prediction-error-rollback-test

So far I no longer reproduce desync in jumpy, and the test I implemented
in that branch is now passing.

framework_crates/bones_framework/Cargo.toml

@@ -117,7 +117,9 @@ document-features = { version = "0.2", optional = true }
 
 # Networking
 [target.'cfg(not(target_arch = "wasm32"))'.dependencies]
-ggrs                   = { git = "https://github.com/gschup/ggrs.git", rev = "0af1a044b96465bd10398947b7fb5e0a34a75f70", features = ["sync-send"] }
+ggrs = { git = "https://github.com/MaxCWhitehead/ggrs.git", rev = "96499377407ce55805a9d0367b86860b74c233bd", features = [
+    "sync-send",
+] }
 bones_matchmaker_proto = { version = "0.2", path = "../../other_crates/bones_matchmaker_proto" }
 bytes                  = "1.4"
 mdns-sd                = { version = "0.10", default-features = false }