Description
I noticed an oddity recently on my module, where after a soft reset, Server v2 would connect just fine but Server v3 would get stuck on "Waiting on network connectivity".
I dug around a bit and found that unlike Server v2, Server v3 additionally checks that m.net.good.sq is true (and also that m.net.connected/m.net.ip are both true, which is pretty reasonable). And even after multiple reboots, m.net.good.sq was undefined on my module, despite m.net.sq being good (see #1149)
But since Server v3 also checks for m.net.good.sq == true, this might cause a situation where a user connected solely over MQTT could accidentally configure a "bad" value for network modem.sq.good and effectively lock themselves out, if they don't have any other way of connecting to their module.
Should we remove the m.net.good.sq check for Server v3, given that Server v2 doesn't check for that either?