If the server was signaled to shutdown when the Node was still waiting
to read its configuration, the configReady channel would never fire,
causing a lockup in NewNode().

We can't do low-level splice() since we don't have access to the raw
socket in the TLS case. This should work for clients though (maybe not
for sources).

This allows usage of HTTPS, IPs won't work well in that scenario.

Remove a lot of boilerplate by using the errgroup package instead of
our own custom cumbersome solutions. Control server lifetime with an
outer Context.

It is best to just make the DNS server listen on all non-loopback IP
addresses from all interfaces. The loopback exclusion is just to
integrate nicely with an eventual DNS cache running on the same host.

And various other minor fixes.

Handle the case when IcecastMount is nil in the template by using the
protobuf getter.

Fix also some errors in the status template, and update to Bootstrap
4.3.1 and JQuery 3.4.0.

It could be that the "n=0 means EOF" semantics are leaking from the
underlying splice() system call? Anyway this prevents radiod from
getting stuck in a busy loop in certain(?) cases.

It's a float encoded as a string.

Unless an explicit fallback is configured. Untested.

* We can't use a RWMutex due to the predictor write at the end
* Return and log errors when lbv2 returns no results
* Generally increase http debug level

Half-closed connections will get sources stuck.

Drop our own XSLT template (yay), we can get the same information
using the built-in /status-json.xsl page with Icecast >= 2.4.