Leverage DazzleConf 2.0 for backwards-compatible configuration improvements

[A248]

DazzleConf 1.x's main limitation is a lack of dynamism with respect to config interfaces.

Migration of previous config versions is unsupported, which blocks LibertyBans from features we might want to implement, such as #202, which require movement and separation of configuration options. In-place transformations are another impossibility, but are required to implement the much-demanded #208 .

There is no way to dynamically include several sub-sections. For example in LibertyBans, we can't place addon configuration under the core configuration. This means that convenient translation is unsupported, because only the main lang/messages_<lang>.yml file is supported for translation (see #222). The segmented configuration also gives the illusion that addons are separate software, when in reality they are more akin to puzzle pieces that fit into bans-core.

[LaurenceBarnes]

Under https://docs.libertybans.org/#/Permissions the docs say:

libertybans.admin.viewips - Allows staff to view IP addresses if censor-ip-addresses is turned on in the configuration.

however, the config option currently is in messages_en.yml, so not consistent with all (I believe?) other non-addon config options being in the main config.yml.

Looks like this issue is a blocker for moving this config option to the correct file.