Refactor Caddy config to use JSON

Since we're programmatically building and manipulating the configuration for the Caddy reverse proxy, I believe it would be more maintainable and elegant to use Caddy's JSON syntax, rather than the default human-friendly syntax.