tests: add failing test case

[zepatrik]

This adds test cases to demonstrate #138
I am not really sure where to start fixing this. It is important to note that the case using draft 2019-09 passes, while it fails when using draft 07.
If there is any direction you can point me to, I will try to fix this.

[GerryFerdinandus]

Additional information.
By removing the "$schema" definition line will also pass the test.

[zepatrik]

I guess because it defaults to the most recent one, that is draft 2019-09?

[ChALkeR]

I'll make a fix for this.
The issue is that schemasafe always adds a type: 'string' default to the propertyNames schema here:
https://github.com/ExodusMovement/schemasafe/blob/81a799a3d577abdc419239bdae1f4890ad60c72e/src/compile.js#L621

But in pre-2019 mode, combining $ref and any other keywords ignores everything except $ref per spec, this is why it complains on unprocessed type.

A simple fix would be to replace { type: 'string', ...names } with { type: 'string', allOf: [names]} on the line above, but I'll recheck if there is a cleaner solution.

As a work-around, { allOf: [{ $ref: ... }] } should work with all versions.

[zepatrik]

Ok nice, thanks for your response 👍

[ChALkeR]

CI didn't fail here as it should have because it was not enabled for PRs from external forks.
Should be fixed in acf9751.

Original issue fixed in aa8fd57.

This is not the correct location for this test, as test/extra-tests/ref.383.json is manually synced with json-schema-org/JSON-Schema-Test-Suite#383 (as are other prs in that dir), but I'll fix (and document) that post-merge. It wasn't documented.
Upd: done in e582f39...4faa854.

Thanks again!