In gluon master, fastd doesn't seem to create a pid file any more. Since
the only purpose was to see if a mesh-VPN connection is establishe, we
can simply check uci instead.

On master nslookup with ::1#54 doesn't work anymore, hence use ::1

Corrected fallback for DNS Request if dmsmasq not working. Added more detailed info to log. Restarting gluon-wan-dnsmasq if neccessary.

Using DNSv4 as fallback, if DNSv6 is not working. Memory-File not longer neccessary, because DNS always gives an answer, even if node is not registered.

b) Stop waiting for batman if gateway list is available even if timeout has not expired.

Analysing of batman gw-list failed, if batman is not in client-mode, or if non-official gateways are in the segment (with local WAN exit).

gluon-config-mode-zip: fix ZIP data not in respondd nodeinfo

gluon-config-mode-zip: i18n: fix translations

respondd plugins have moved from /lib/gluon/respondd/ to
/usr/lib/respondd. Reflect this change in the Makefile to ensure
respondd will find our plugin.

Use the correct translation namespace. As we run in gluon config mode,
we do not have our own controller. Thus we need to specify the
translation namespace for gluon to find translations. See
<https://gluon.readthedocs.io/en/stable/dev/web/i18n.html>:

> Note that translations are namespaced: each package will only use its
> own translation strings by default. For this purpose, the package name
> must by specified in a package’s controller. It is possible to access
> a different translation package using the i18n function from models
> and view, which is necessary when strings from the site configuration
> are used, or packages do not have their own controller (which is the
> case for config mode wizard components).
>
>     local site_i18n = i18n 'gluon-site'
>     local msg = site_i18n._translate('gluon-config-mode:welcome')
>

Modification for use with LEDE: local DNS-Forwarder format = ::1#54 (without square brackets, and hash instead of percent)