Dont know

Resolve TMSS-154

Closes TMSS-154

See merge request !103

# Conflicts:
#	SAS/TMSS/src/tmss/tmssapp/migrations/0002_populate.py
#	SAS/TMSS/src/tmss/tmssapp/populate.py
#	SAS/TMSS/src/tmss/tmssapp/viewsets/scheduling.py
#	SAS/TMSS/test/tmss_test_data_django_models.py

Resolve TMSS-153

Closes TMSS-153

See merge request !102

TMSS-153: moved default_specificaton and parset methods from view functions to viewset methods, and annotated them with swagger documentation. This way they are automatically part of the swagger API pages

TMSS-154: Fix in unitttest, taking 'history' into account and determine the total of subtasks objects in stead of hardcoded number

TMSS-153: added little factory to pick the proper conversion method based on subtask spec template name

TMSS-153: and TMSS-145: fixed populate.populate_lofar_json_schemas according to https://support.astron.nl/confluence/display/TMSS/UC1+JSON
There are now two Task schema and 1 Subtask schema.
Used the schema's, added dataproducts, convert everything to parset.

TMSS-153: added most parset keys according to https://support.astron.nl/confluence/display/TMSS/UC1+JSON
still working on the quite complicated dataproducts

TMSS-153: removed strange string conversion lines which do not appear to be needed anymore now that we use python3. And if we do need the conversion, then this implementation is wrong, as it converts everyting to string, not just unicode-strings

TMSS-153: added json_utils and tests. method get_default_json_object_for_schema returns a valid json object for the given schema with all properties with their default values