This adds mesh_on_lan functionality.

A new optional site.conf option, mesh_on_lan, has been added. If set to
'true', all LAN ports will be used for meshing instead of being part of
the client bridge.

This will introduce a new nodeinfo object, network.mesh.bat0.interfaces,
containing any of the the following subordinated objects:

- wireless
- tunnel
- other

Each of these objects contains a (possibly empty) list of MAC addresses
(lowercase, colon-notation) corresponding to a interface of the given
class. Combined with a batman graph it is thus possible to mark
sub-graphs as "wireless" or "vpn".

The previously used object mesh_intefaces is superseded by this new
object structure and mesh_interfaces will be removed in a future Gluon
release.

Directly using libiwinfo is more reliable.

It would be nice to generalize this to work with multiple radios, maybe by
integrating it into the wifi-config module...

Fixes #219

All other titles are grey, the magenta-colored section titles inbetween look
weird.

This allows to reach the node in setup mode over the same link-local IPv6
address as br-client uses during normal operation.

OpenWrt doesn't set the regdom unless a WLAN device is started. Explicitly set
the regdom in the setup mode to get the correct list of allowed txpower entries
in the planned LuCI module.

gluon-mesh-batman-adv-core: fix the data types in the check_site.lua

Add the package gluon-luci-wifi-config

This seems to mitigate weird bridge forwarding issues.