Reduce commit spam by moving container information elsewhere

[onedr0p]

While I love the idea of having these containers and badges it does come at an expense of having a lot of spam in the commit log. Ideally it would be great to move these to outside the README maybe in the Github wiki?

[rtrox]

Yea... this is getting sort of spammy, especially with all the minor version changes. contributor doesn't give me access to set up wiki pages, but if you want to get a skeleton wiki set up, I should be able to work on the automation to write there. It looks like the wiki is just a hidden git repo, so it shouldn't be too crazy to get it moved over:

https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages#adding-or-editing-wiki-pages-locally

[onedr0p]

@rtrox I wonder if it's better to just remove it, while not ideal people can visit the packages section to see images and tags.

The wiki idea isn't great because it's also moving it out of sight like the packages section would be. I think this can be revisited when shields.io supports GHCR?

It would kind of work like this https://github.com/eggplants/ghcr-badge (not sure if we want to use this project though)

See this for an example: https://ghcr-badge.egpl.dev/onedr0p/prowlarr/tags

Using shields.io / ghcr-badge.egpl.dev would make it so commits are only added on addition or removal of images.