Include local update flags in login message

* local_auto_update_enable
* local_manual_update_enable
Load more stuff before starting adept connection

This makes the content get loaded for the new login arguments before the login request is sent.
Allow halt to be requested if so enabled.
Fuzz reconnect interval connecting to FlightAware

If the adept server shuts down and drops all the clients, they all delay 60 seconds and try to reconnect, which is a lot of connections all at once, which is kind of staggering to the infrastructure.  By fuzzing the delay between 60 and 120 seconds (instead of a fixed 60 seconds) it will at least somewhat spread out the connection attempts, though they will still be frequent.

If the server is down more than a couple minutes then when it comes back up the connections should be pretty randomized with 100% of the remotes making connection attempts within two minutes.
Add a -showtraffic option to piaware
Server message handling improvements

* Don't continue through the handler if we get an error reading from the server socket.

* Don't try to log errors in messages theoretically received from the server back to the server.
After connection loss wait 60s before reconnecting.
Disconnect/reconnect after an error due to a server message

This should interrupt the runaway logging problem even though we aren't sure what's causing it.
Version bump to 1.17.
Don't even try to forward "connecting" log messages

* Although piaware shouldn't even attempt to send a log message unless connected don't try to forward "connecting" log message to server.
Fix reconnect command.
Update comment about inspecting source

A couple of procs had been merged into a singple proc and the comment didn't reflect that.
Remove superfluous certificate authority checks

They didn't really provide anything and they might royally screw things up in about 13 months when our certificate expires.
Don't run rpi-update as part of the full update.
Make parse_mac_address_from_line work properly.
Get mac address from wlan0 or whatever, if no eth0
Use log_locally to report an alternet mac address

Using logger at that point causes an infinite recursion.
Cache the mac address once it is determined.
Log the full version, like 1.17-2, with login

...along with the previous one that's just like 1.17
Include full version in login message.