fix: improve new v1 apis to use mqtt lazily and work entirely locally

[allenporter]

The new v1 channel will:

• prefer local connection, using cached network information
• establish mqtt connections on demand only when needed on first subscription. we can decide to poke the mqtt session explicitly if we prefer, but it won't be done by the device manager now
• refresh network information on the first failed attempt, then once every 12 hours
• retry local connections with backoff

This makes the local background task (per device0 now work similarly to the mqtt session task.

The background logic is difficult to unit test without races, so it is not tested. I will do additional manual testing of complex scenarios for errors when this is integrated into Home Assistant.

[Lash-L]

Honestly looks good, one small nitpick, feel free to ignore.

establish mqtt connections on demand only when needed on first subscription. we can decide to poke the mqtt session explicitly if we prefer, but it won't be done by the device manager now

We may want to poke it explicitly in HA for the sake of getting protocol updates, but I think this good library wise and we can figure out protocol updates later.

[Lash-L]

could simplify by setting use_cache = True inside the if statement for >1. One fewer if statement

[Lash-L]

although i guess you'll have to move that elif below.

You don't have to do this if you don't want to. If you think it hurts readability or understandability, just ignore

[allenporter]

Yeah i looked at doing that before, but its like this because there are a couple scenarios for deciding if cache should be used that it makes sense to do them at once. So, I decided to instead extract to a helper function so at least this flow is a little easier to read.