message: fix: Message sorter shouldn't clone message when registering
  We were cloning the message when registering it to a future, meaning
  we would set the id then drop the cloned message, so every message
  still had an id of 1. Oops.
diff: @@ -71,8 +71,7 @@ impl ClientConnectorMessageSorter {
  /// that id with the future to be resolved when we get a response back.
  pub fn register_future(&mut self, msg_fut: &mut ButtplugClientMessageFuturePair) {
  trace!("Setting message id to {}", self.current_id);
  - let mut msg = msg_fut.msg.clone();
  - msg.set_id(self.current_id);
  + msg_fut.msg.set_id(self.current_id);
  self
  .future_map
  .insert(self.current_id, msg_fut.waker.clone());
  