import schemas

To consider:

- Should the module types without a specific schema default to module - **yes - it does in spotlight**
- What's up with tabs? Why is there not availability type? - **tabs seems to contain all the availability modules, perhaps we can leave this for now and handle validating sub modules in tables as a tech debt story (already created).**
- Solihull is very wrong - **Use this json:**
```
{"axes": {"y": [{"label": "Reports last week", "key": "missed_bins:sum", "format": "integer"}, {"label": "Percentage of total reports", "key": "percentOfTotal(missed_bins:sum)", "format": "percent"}, {"label": "Change since previous week", "key": "delta(missed_bins:sum)", "format": {"showSigns": true, "type": "percent"}}], "x": {"key": "ward", "label": "Ward"}}, "sort-by": "ward", "sort-order": "ascending"}
```
- hmrc-prototypes-hmrc-operations is wrong - **delete empty module**
- Add validation on the validate method - not as part of the api - **Later**
- what does clearer errors mean? - **Later**
- continue with draft3? - **Yes, though it's pretty lenient about what a valid schema is...**
Would be really good if you could explain what this is either in the commit or the PR