Feature request: JSON config format

# Use case

Maddy's uses a custom config format. This makes it hard to integrate maddy with solutions for automatic configuration management (both generating maddy config or parsing maddy config). NixOS for example can very easily generate JSON from it's structured module system, but it is much harder to generate the current maddy config format in a meaningful way from nix.

# Your idea for a solution

I propose to introduce a canonical JSON representation of the configuration and a way to convert from the current configuration format to the JSON format (similar to how Caddy uses the human readable Caddyfile format and a machine readable JSON format). This also makes it easier to write various adapters that can translate from other mailserver config (e.g. dovecot) to the equivalent maddy config on a best effort basis (similar to how Caddy has adapters e.g. for nginx).

- [ ] I'm willing to help with the implementation

The issue names no files, tests, or entry points. Start by understanding the existing configuration format and deciding the scope of the canonical JSON representation and both conversion directions; done means the schema and conversion behavior are defined and implemented.

Written by the indexing model from the issue text.