TMSS-272: renamed schema files to more consistent file naming convention. Added populate script and config file. Deploy all schema files in share.

TMSS-272: derive from common AbstractTemplateViewSet which implements common actions to get the schema or a default json blob

TMSS-272: add title/description/version to schema for each template so each schema is properly annotate. Validate the schema itself against its own schema

TMSS-272: cleaned up SAS/TMSS/src/tmss/tmssapp/validation.py validation code from tmss. Moved remaining clean code into LCS/PyCommon/json_utils.py

TMSS-272: use improved JSONEditorField which automagically uses the pointed-to-schema for the html editor

TMSS-272: when creating/updating the DRF field method to_internal_value is called; make sure that all urls are pointing to the correct host. When getting the DRF field method to_representation is called. Make sure we massage the data such that our html json editor can handle the schema (with all refs resolved)

TMSS-272: made working example with reusable schemas. Validation works both server-side and client-side in the json-editor widget. For the json-editor widget we need to resolve absolute URL refs as a workaround

TMSS-272: modified the JSONEditorField such that it uses the  from the jsonobject itself. This implies that we should inject the proper url for the  in all our json blobs (TODO). Extended a special version of the JSONEditorField: JSONEditorSchemaField which automatically makes sure that all  point to the correct tmss host.

TMSS-272: initial version of a way to store common json schema's in a CommonSchemaTemplate model, and inject the  uri's with the base url to make them navigatable

TMSS-291: Fix Django version to prevent import errors on DRF

Closes TMSS-291

See merge request !189

TMSS-287: implemented CycleQuota

Closes TMSS-287

See merge request !188

TMSS-287: added Quantity AbstractChoice model, and used it in ResourceType to annotate each resource type with the correct quantity.

TMSS-287: upon request of the frontend team, added more test data and added some scheduled/blueprinted tasks as well. Use TMSS_UNIT_TESTING envvar to skip expensive example data setup.

TMSS-287: indicate (via environment var) that we are using the TMSSTestEnvironment during unittesting.