Compliance monitor: add endpoints to render certificate scopes

[mbuechse]

Currently, we rely on some JavaScript code in the docs repository to render our certificate scopes nicely. Needless to say, the code in the docs repo easily diverges from the code in the standards repository, see, e.g., this recent bug issue or this feature issue.

Therefore, I'd like to have the all relevant code in the standards repository.

• Either the actions in the docs repo continue to execute the code, but they get the code from here. (They already do check out this repository for the data.)
• Or this repo gets new actions that render the documents, and the actions in the docs repo somehow get the rendered documents from this repo.
• Or our beloved Compliance monitor (which already uses Jinja2 templates to render result data) renders the documents, and the actions in the docs repo get them from there. Something similar is going to happen with the table of partner clouds, see this issue.

I propose the third option.