Windows Lobby WebSocket can get closed down

[ctm]

Fix so the Lobby session on a Windows build won't expire.

This is an unfortunate consequence of how Windows handles background windows. In theory, putting the WebSocket connections into the Tauri "backend" may solve that problem, but of course it means that the info that is received then needs to be sent to the front-end. I don't think that's needed on macOS, nor does Google's AI. So, I'm reluctant to do a refactor just for Windows, especially before looking real hard for a less drastic solution.

[ctm]

Although I didn't write it down at the tine, I've seen this on macOS, too. As such, I think I need to seriously consider having all the WebSocket stuff done on the backend, which I think I can have AI do fairly easily, once I research what should be the appropriate mechanism for the backend to communicate with the front-ends.