Comms uplift

[SergeBakharev]

Changes:

• Enhancement: Autodetect Smoothie vs Makera communication protocol on connect and use it for the session
• Enhancement: Show a connecting progress popup while opening a USB device
• Enhancement: Log connect and manual disconnect with the connection method and address
• Enhancement: Add a "Network..." option under Scan Wi-Fi in the connection dropdown to enter a machine network address
• Enhancement: Reconnect supports USB as well as WiFi. Configure preferred method for app-launch auto-connect in Controller settings
• Change: Auto-connect on app launch now is only performed if auto-reconnect is enabled
• Change: Reconnect uses the last successful connection method. On fresh app launch it uses the configured preferred connection method
• Change: USB devices in connection dropdown are filtered to only show devices specifically with the FTDI chip found on the Makera machines
• Change: USB devices are now selected and stored by stable VID:PID:serial identity (instead of generic COM path)

Resolves: #560 #491

I tested with the Makera native firmware on the machine, as well as both modes from the new switchable code from PR343

It was even able to update the machine firmware from running 1.0.6 Makera to our Community version. So I'm pretty confident in all that.

Where I'm less confident is in the protocol abstraction, so in future we can implement our own thing. I'm having difficulty imagining what that might look like, probably doesn't have to be perfect today. But I would still appreciate those comments.

As part of the USB changes I made it filter the USB device selection to just the FTDI chip, and record the device serial to config for reconnect. This works well on my MacOS machine, if someone can help test this on Windows that would be awesome

[SergeBakharev]

I'm noticing a race condition for the continuous jogging keep alive. Fixing....