Fix seat claim registering wrong key in ping tracker

_updateSeat passed [true, value, 0] to _handlePing but the signature
is ([playerIdOrCount, latency]), so `true` was stored instead of the
playerId. The stale-connection sweep then cleared the seat immediately.

src/store/socket.js

@@ -645,7 +645,7 @@ class LiveSession {
       this._store.commit("players/update", { player, property, value });
     }
     // update player session list as if this was a ping
-    this._handlePing([true, value, 0]);
+    this._handlePing([value, 0]);
   }
 
   /**