respondd has to handle interface changes for re-listening
respondd was being sent sighup by procd previously,
but didn't handle it
The easiest way is to just restart respondd to make it re-listen,
since it does not carry any important state
Because we unconditionally appended `-i br-client` to the command line of
respondd, it wasn't restarted when br-client changed state. Now, we use a
jsonfilter expression on the network.interface dump data, similar to how the
other interface names are generated, and only add the interface to the argument
list if it is up.
Instead of starting gluon-respondd from a hotplug handler, add a proper
init script. The new init script has a restart_if_running argument which
is now used by the hotplug handler.