Introduce compatibility list with compilers for library vendors and users

Currently we offer only a list of which libraries are available to select from, and then eventually the user finds out if it actually works or not.
For the non-header-only libraries that we build, we have a way of actually knowing which commit was able to be built by which compilers.
We can offer a page of compatibility + incompatibility per library version or trunk commit.
The only problem is that once we rebuild for a new trunk commit, the information about the previous commit gets lost.

Perhaps we can also offer status badges? Not sure in what form though

Todos
- [x] Storage? -> DynamoDB table `library-build-history`
- [x] Proof of concept
- [ ] Fill with data during library build-process
- [ ] Make endpoint for a badge
- [ ] Support Rust and Fortran
- [ ] Turn into lambda on our api gateway
- [ ] Make known to library maintainers
- [ ] ?

Start with the proof of concept and the DynamoDB table named library-build-history, then trace the library build process and API Gateway/Lambda integration described in the issue. Clarify which remaining item is in scope; completion could mean recording build results, exposing a badge endpoint, adding Rust and Fortran support, or moving the service to Lambda.

Written by the indexing model from the issue text.