feat: serve schemas based on which tags exist on gh

[jo-mueller]

PR following #564 that solves the problem a bit more elegantly (I hope):

This PR changes the build process of the page so that the following happens on build:

• All tags on ome/ngff-spec are automatically retrieved with git ls-remote --tags https://github.com/ome/ngff-spec
• This gives a list of tagged versions on that repo (currently not listing 0.1 ... 0.5)
• Copy all the schemas over here and serve them under the respective tag.

This way, we should be able to access the schemas of all past (we'd need to tag them) and present through the ngff page, including the dev versions. This also centralizes the tagging over at ngff-spec as a core mechanic to make schemas available through the ngff page.

cc @jni

[github-actions]

Automated Review URLs

• Readthedocs

[jo-mueller]

@lubianat do you have ideas how to make this nicer? I tried a few things with redirects, but maybe the RTD redirects supersede any redirects to outside pages (i.e. via an htaccess file) I am defining here, which is annoying.

To have the browser render the schemas as text instead of downloading the files instantly, we would need to rename the files into .json, I think.

[lubianat]

@jo-mueller should we go ahead and add the .json for the next releases (per #462)?

I don't have a suggestion on how to make it nicer, though

[jo-mueller]

We could serve them as both *.schema and *.json? For the time being, this could also happen here until we make the change at ngff-spec?

[lubianat]

We could serve them as both *.schema and *.json? For the time being, this could also happen here until we make the change at ngff-spec?

I don't have a good perspective on the implications. I guess we can do it at least transitionally, while tools move towards .json or .schema.json