apidom-reference: enhance error reporting

[char0n]

Enhancements will probably be specific to resolution and dereferencing (worth confirming before). It is currently not really possible to determine where (doc, line, column) the error actually happened. The goal of this issue is to produce errors with more information about what actually happens, why and where:

We can start with decorating errors with following information:

• sourcemap (if available)
• reference-value metadata
• cross document boundary JSON Pointer
• URI of the current reference

TODO:

• AsyncAPI 2.x dereference strategy
• OpenAPI 3.0.x dereference strategy
• OpenAPI 3.1.0 dereference strategy
• AsyncAPI 2.x resolution strategy
• OpenAPI 3.0.x resolution strategy
• OpenAPI 3.1.0 resolution strategy

[char0n]

First we need to get rid of babel-plugin-native-error-extend plugin and take full control over how we extend native errors.

[char0n]

New monorepo package called @swagger-api/apidom-error has been introduced in #3067:

Main things that this package handles is:

• bypass complicated extensions of native Errors
• backward and forward compatible support of error chains

Next thing is to integrate the package in other packages a get rid of babel-plugin-native-error-extend.

[char0n]

@swagger-api/apidom-errors package is now exclusively used to create error hierarchies. Addressed in #3068. babel-plugin-native-error-extend has been removed and the complexity of error extensions and compatibility is handled exlusively in @swagger-api/apidom-errors package