* Make /api/format handle multiple formatter types
* Ignore preferred style if the formatter is a 'one true style' formatter
* Add tests for base formatter
* Document /api/formats and /api/format/<formatter> usage
* Document adding a new formatter
* Update amazon config
Co-authored-by: Matt Godbolt <matt@godbolt.org>
We still support /shortener (though will scrape logs to see when
we can remove).
The route under /api/shortener will have the CORS headers set up
properly for things like @foonathan's lexy visualiser.
* dont return all compilerproperties always in /api/compilers
* fields=all ipv ?all
* use fields=all with remote instances
* add to documentation
* cover more paths with tests
