Splitting OTA (over the air update) between test and production

When building, it's easy to fall into the trap of calling every device 'test', and upload every new binary to every device. As we get closer to shipping, that's not good. So, went back through and cleaned up the existing code to indicate early whether a device will be 'test' or 'production'. On start, the device looks for the latest version, test for test, production for production. This allows us to ship production devices, run test devices, and only post a production version after it's been thoroughly tested. Kind of common sense, but with the dual processors on the ducore board, a bit more complex. Image shows the interface for the db that tells the board what device it's going to become. What's new is the 'Environment' switch. For now, a device will always be one or the other. It would be possible in the future to use MQTT to tell a device to switch, but currently don't see much benefit in that.