fix: use ApiDOM@0.76.1 to be further compatible with Node.js>=12.20.0 (#3129)

Refs #3127

Author: char0n

package-lock.json

@@ -114,10 +114,10 @@
   },
   "dependencies": {
     "@babel/runtime-corejs3": "^7.20.13",
-    "@swagger-api/apidom-core": ">=0.74.1 <1.0.0",
-    "@swagger-api/apidom-json-pointer": ">=0.74.1 <1.0.0",
-    "@swagger-api/apidom-ns-openapi-3-1": ">=0.74.1 <1.0.0",
-    "@swagger-api/apidom-reference": ">=0.74.1 <1.0.0",
+    "@swagger-api/apidom-core": ">=0.76.1 <1.0.0",
+    "@swagger-api/apidom-json-pointer": ">=0.76.1 <1.0.0",
+    "@swagger-api/apidom-ns-openapi-3-1": ">=0.76.1 <1.0.0",
+    "@swagger-api/apidom-reference": ">=0.76.1 <1.0.0",
     "cookie": "~0.5.0",
     "cross-fetch": "^3.1.5",
     "deepmerge": "~4.3.0",

package.json

@@ -321,7 +321,7 @@ describe('dereference', () => {
               expect(errors).toHaveLength(1);
               expect(errors[0]).toMatchObject({
                 message: expect.stringMatching(
-                  /^Could not resolve reference: Evaluation failed on token/
+                  /^Could not resolve reference: JSON Pointer evaluation failed while evaluating/
                 ),
                 baseDoc: expect.stringMatching(/unresolvable-path-item\/root\.json$/),
                 $ref: '#/paths/invalid-pointer',