Add querying version numbers / getting staging version for a resource

[jmetz]

As discussed with @FynnBe , this is likely to require a versions.json (or similar) at each resource's root, listing the versions and their publishing status.

@FynnBe @oeway :

What structure would you think is best for such a file?

I'm currently thinking:

{
    "1": "published", 
    "2": "staging", 
}

[FynnBe]

btw, we should keep the following scenario in mind:

1. user uploads a staged model
2. CI starts testing model
3. user edits staged model
4. CI finishes
5. maintainer sees CI result of outdated version

[FynnBe]

one possible solution to this is to use additional status values, but it would be nice to keep it as simple as possible.

[jmetz]

So like "testing" - to indicate it's locked for editing or something?

[jmetz]

Which would mean a user can't edit their staged model until the CI ends.. not ideal, but possibly better than the alternative?

[jmetz]

I think we should keep it simple - a user can edit their staged entry, and the fact that that will possibly waste a bit of reviewer time is what it is.. 🤷

[jmetz]

This now depends also on https://github.com/bioimage-io/bioimageio-uploader/issues/59

[jmetz]

closed with 48a39ba

[jmetz]

This was done in https://github.com/bioimage-io/collection