Switch to non-deprecated remote schema referencing #685
Description
Bug report
What is the current behavior?
We're getting/resolving remote JSON schema in a deprecated (and possibly uncached) way
What is the expected behavior?
We resolve once per runtime according to best practice and the cache is used after that.
Proposed Solution
- Switch to the above approach
- Test that the schema is being cached