SPIKE: Consider migrating to @apidevtools/json-schema-ref-parser

[daniel-white]

• @stoplightio/json-schema-ref-parser has a lot of tech debt: broken tests, no CD release, written in javascript
• @P0lip says we might be able to move over

there are a few key features that we must have in @apidevtools/json-schema-ref-parser in order to adopt it

1. setting custom user agent for http resolver
2. ensure basic auth is translated into an Authorization header from a url
3. improved error message for unresolvable JSON pointer segments (Prism issue, PR)

There are likely other features that I'm not aware of that in our fork, we added.

What questions to answer:

1. what changed in our fork that the upstream doesn't have?
2. are any of those critical still?
3. how much work would it take to build in any features we need to retain in the upstream repo?