Steps to reproduce:
- deploy the standard type Note
- then deploy a new document type SubNote that extends the Note type
- then deploy another type that overrides the existing Note type to add a schema to it
=> the document type SubNote does not hold the new schema
This ordering problem is visible in Studio, where order of document types registration did not take into account their hierarchy (fixed by NXS-836)