(cherry picked from commit b313a631)

Signed-off-by: David Bauer <mail@david-bauer.net>

(cherry picked from commit bf8c3bab)

Signed-off-by: David Bauer <mail@david-bauer.net>

(cherry picked from commit 7f3a3042)

(cherry picked from commit 447595f0)

(cherry picked from commit 63ebeb25)

(cherry picked from commit 239c379d)

Add the `wifi5.outdoor_chanlist` site configuration that
allows specifying an outdoor channel range that can be
switched to for regulatory compliance.

Upon enabling the outdoor option the device will
 - configure the `outdoor_chanlist` on all 5 GHz radios
 - which may enable DFS/TPC, based on the regulatory domain
 - disable ibss/mesh on the 5 GHz radio, as DFS *will*
   break mesh connections
 - allow for htmode reconfiguration on 5 GHz radios

The outdoor option can be toggled from
 - Advanced Settings
   - W-LAN
     - Outdoor Installation

The `preserve_channel` flag overrules the outdoor channel
selection.

In multidomain setups, VXLAN is enabled by default, but can be disabled in
domain configs using the mesh/vxlan option. In single domain setups, the
mesh/vxlan option is mandatory.

The UCI option for legacy mode is removed.

Fixes #1364

At the moment, we don't have a good guideline for package-specific
configuration, but it seems like a good idea not to split configuration
into too many tiny pages, especially for packages that aren't commonly
selected explicitly.

Some uncommon configuration is dropped from the example site.conf to remove
clutter.

* change type of next_node.name
* create domain entry for each entry and add to dnsmasq configuration

[Matthias Schiffer: reword documentation]

[Matthias Schiffer: rebase]

Without -v, hexdump would sometimes replace duplicate bytes with "*" and
a newline.

The next-node MAC address doesn't need to be unique in different
communities, so we can as well add a default value.

The SSID for the mesh network should be cryptic, otherwise some users will try to connect to that network and have a bad user experience.