read the sector command fields the way round they are sent

the checksum goes out first and the tick second: setClientChecksum writes
[+0x50] and setClientTick writes [+0x54], and encode writes [+0x50]
before [+0x54]. we had them the other way about, which is why the log
showed a tick full of noise and a checksum climbing by forty-one a
message - the tick was being read as the checksum.

crates/logic/src/messages/sector_command.rs

@@ -4,9 +4,9 @@ use crate::commands::LogicCommand;
 #[message(id = 12904, direction = "client", name = "SectorCommandMessage")]
 #[codec(partial)]
 pub struct SectorCommandMessage {
-    #[codec(vint)]
-    pub client_tick: i32,
     #[codec(vint)]
     pub client_checksum: i32,
+    #[codec(vint)]
+    pub client_tick: i32,
     pub command: Option<Box<dyn LogicCommand>>,
 }