New config format, MQTT support and other small improvements :)

To simplify configuration of the device now all settings are in a single place!

Format syntax:

• empty lines and lines starting with a hash (#) are ignored
• other lines are expected to be in key=value format

If lists are needed there are tools to split strings on commas, so it's possible to specify multiple owmIds like this:
owmId=1,2,3,4,5

The old config is not migrated, you will have to update it yourself by hand.

The LHC task is still disabled (and now it's even broken), code for Fixxer.io was removed.
New SerialCommandTask is available to query the device.
$var_name for readout of variables (including things like up-time and ip address
$var_name=value to set variables (to test something quickly by changing params)
reboot :)

There's also an MQTT task that can report LocalSensorTask readouts and also replies to variable requests.
By default the device name is InfoClock.

Lockdown counter replaces Brexit counter

v.0.4.4

Removed brexit code, added generic stateless msgs

No more display constants!

This release contains two important changes:

1. the number of display segments and the brightness is no longer a compile time constant:
   You can configure it via the web interface - reboot will be required to change the number of segments.
2. A new task has been added that can read currency exchange rates from http://fixer.io (currencies can be configured).

And some other small changes:

1. The configuration variables are available earlier making it possible to use them in task constructors.
2. More clocks! (Jerome wanted more ;))
3. Some even smaller code improvements :)

New LHC Status data source, code cleanup :)

This release contains two major changes from 0.2.x releases.

1. It contains a new code for reading LHC status. The old one had some problems, the service wasn't always reliable. it has been replaced with a simpler code that reads status from the ALICE experiment and does it every minute. Tje update rate of the service is 2 minutes so although it's slower to refresh than the previous one it's more reliable.

2. I have removed a lot of old code that wasn't used any more.