Lag on Windows for signon

[ctm]

FIx so either people can log in immediately at the start or they're given some sort of useful feedback.

When I start the Windows client, it auto fills my account and password if I'm still logged in since the last time I logged in, however, the demo button is disabled but the Enter is enabled, but won't work. A few seconds later the demo button will enable and Enter will work. I don't think it used to do this, but it's been a while since I've run the Windows client.

My recollection is that both the Demo and Enter buttons were supposed to be enabled only when the WebSocket was connected, which makes me wonder how they start out different. I also don't understand why Windows is the only client where I see this lag, but when I logged into Windows for the first time in while it looked like the OS may have been updated recently, because it asked me to do a bunch of setup things. My suspicion is that the two are related.

It shouldn't be too hard to figure out what's going on, but I don't think I need to look into it until someone other than I is using the Windows client.

[ctm]

<button ref={self.demo_ref.clone()} type="button" onclick={demo_onclick} disabled={!self.is_connected()} uk-tooltip="Creates a tiny tournament where you play against yourself">{"Demo"}</button>

vs.

                        <button uk-tooltip={nick_tooltip} ref={self.enter_ref.clone()} tabindex={3} type="button" disabled={!self.is_enterable()} class="uk-button uk-button-primary" onclick={enter_onclick}>
                            { "Enter" }
                        </button>

    fn is_enterable(&self) -> bool {
        self.logging_in_info()
            .is_some_and(|info| info.valid_nick() && !info.password.is_empty())
    }

So, is_connected() isn't necessary for Enter to be enabled. That does not look right and I suspect that's a regression. This strongly suggests that the initial web connection is taking a while to be made though.