Expired Session using Tauri client #1689
Description
Fix the bug that causes the macOS Tauri mb2 client to give an "Expired Session".
This is quite possibly the same issue as "Already logged in", but I'm treating them differently in part because that one has a lot of comments and it may make more sense to look at this with a fresh eye.
I'm now using Tauri builds to play the evening craftpoker.com game. I'd like to use it on my phone, but I haven't finished my SPA integration (#1651). Yesterday I saw "Expired Session" when I highly doubt I'd have seen it had I been using the web version, and that got me thinking about pings. However, before creating this issue, I simply fired up the macOS Tauri client and a Safari client, logged deadhead into Tauri and dh2 into Safari and then went about doing other things. Neither were the top-most application, which I think is important to note because one confounding factor is that I spend a lot of time in the browser doing other things when I'm logged in and "normally" everything is on Brave. So, macOS might simply be favoring the top-most application. However, I brought both clients to the fore and the Tauri one had "Expired Session" and the Safari one didn't.
I should be able to tell more about what's going on if I instrument the client to log when it gets disconnects and when it tries to reconnect. It probably also makes sense for me to log when a session is destroyed on the server. It's possible that both the Tauri and Safari clients lose their connections at the same time but that Safari simply reconnects successfully. My guess, however, is that Safari doesn't lose its connection at all.
OOPS: as I was writing up this issue, I glanced at ping.rs and I see that we use 30 seconds for a ping interval, rather than 20, which is suggested on the web. As such, in addition to what I describe above, I'll also change the interval down to 20 seconds and also log to the console when we send pings.