Map errors raised by `validateJSON` back to their original source files

[ewanharris]

When we run the fully combined model through validateJSON currently the errors have no metadata associated with them that would allow us to (or at least easily) look up the line and column information associated with the error.

When we raise a validation error we should include the new file and module metadata fields so that we can improve the error reporting for these errors. Then in the catch for validateJSON we can lookup the file contents and get line/column data to improve these errors.

[ewanharris]

Current status of error types (as listed in errors.ts):

• "schema-version-required" ❌ wont do, check should be in transform
• "schema-version-unsupported" ❌ wont do, check should be in transform
• "reserved-type-keywords" ✅
• "reserved-relation-keywords" ✅
• "self-error" ❓ this doesn't seem to be referenced anywhere
• "invalid-name" ✅
• "missing-definition" ⚠️ In progress
• "invalid-relation-type" ⚠️ In progress
• "invalid-type" ⚠️ In progress
• "relation-no-entry-point" ❓ Can't do without a third error project
• "tupleuset-not-direct" ⚠️ In progress
• "duplicated-error" ❌ wont do (already handled in transform)
• "allowed-type-schema-10" ❌ wont do
• "assignable-relation-must-have-type" ❓ this doesn't seem to be referenced anywhere
• "allowed-type-not-valid-on-schema-1_0" ❌ wont do
• "invalid-schema" ❌ wont do, check should be in transform
• "invalid-syntax" ❓ this doesn't seem to be referenced anywhere
• "type-wildcard-relation" ⚠️ In progress
• "condition-not-defined" ⚠️ In progress
• "condition-not-used" ⚠️ In progress