Move message_queue over to deduplication via intents

Due to each service having multiple distinct clocks, we can't expect a stable
ordering except the ordering an intact message-queue provides. The messages
emitted should be consistent however, solely with unknown order, which is why
we can craft intents based on their contents (already implemented by
processor-messages).

message-queue/Cargo.toml

@@ -20,6 +20,7 @@ serde = { version = "1", features = ["derive"] }
 
 # Encoders
 hex = "0.4"
+bincode = "1"
 serde_json = "1"
 
 # Cryptography