Proposal: maximise ease of scivision model and datasource setup with different levels of inclusion in the catalog

[edwardchalstrey1]

Following on from #515 I propose the following:

1. There should be three categories of scivision model and datasource, labelled with different coloured badges in the website model/ds grids like:
   • Status: Use with Scivision.Py where the model/ds works with load_dataset or load_pretrained_model
   • Status: Use with Homepage instructions where the model or datasource does not work with the Python package, but has tested documentation that a user can follow to use it
   • Status: Development where there is a link to an unstructured datasource or model package that is under active development. There should still be some documentation but it doesn't need to be tested for replicability. (this could even be a separate bool, maybe Status: Active development vs Status: Complete or similar)
2. The "add new datasource" and model forms should be simplified such that the requirements for Scivision.Py functionality are only shown towards the end, or drop down on a checkbox... something like this. The readthedocs can then be linked to (an updated version if needed) only as a requisite for the Python version
3. Projects could also have Status: Active and Status: Complete based on dates?

Some extra thoughts on improving the forms are collected here

[ots22]

Closing this - planned changes to new model/data flow in #616