Add reports generation system

[eitsupi]

Suggested by #181 (comment)

Add a script and a report template to create reports about the contents of the container images.
By publishing the generated Markdown files on GitHub (maybe on the wiki?), users will be able to go back and examine past images.

The report will look like this:

To create reports, we will need files in tmp directory about the container images created by the following command. (need docker)

$ make inspect-image-all

Next, run the following command to generate reports in the reports directory. (need R 4.1 and the tidyverse packages etc., I run this command in rocker/tidyverse:latest)

$ make report-all

ToDo

• Add jobs to the Makefile
• Python packages list
• commit hash Cannot be implemented at this time because it is necessary to set the org.opencontainers.image.revision annotation when building images. I would like to set this up after we change the build method to one using buildx bake. ([Tracking] Use buildx bake to build images #199)

[eitsupi]

@cboettig @noamross Now we can generate simple reports, what do you think about this?

If you would like to adopt the idea of publishing these reports on the wiki, I think we can do so by incorporating the following functionality into the GitHubActions' workflows.

1. After the docker build is finished, run make inspect-image-all to store the files in the tmp directory.
2. Use the upload-artifact action to store the tmp directory.
3. Start a new job in the rocker/tidyverse:latest container.
4. Check out this repository.
5. Use the download-artifact action to restore the tmp directory.
6. Check out the wiki in the reports directory.
7. Run make report-all.
8. Use the stefanzweifel/git-auto-commit-action to upload new reports to the wiki.

[cboettig]

@eitsupi this looks great. Yes, I think adding the GitHubActions workflow to publish to the wiki would be a great idea.
I'll merge this as is and then we can take a look at the Wiki integration in as a separate PR.