fix(deps): upgrade jsonpathly to 3.0.0

As part of [0], it was noted that the upstream library we use for JSON
Path expressions isn't fully RFC 9535 compliant.

With help from Claude Sonnet 4.5 to help diagnose a change in the public
API for jsonpathly, where a single quoted path is returned.

Co-authored-by: Claude Sonnet 4.5 <jamie.tanna+github-copilot@mend.io>

[0]: atamano/jsonpathly#12

Author: jamietanna

package-lock.json

@@ -101,7 +101,7 @@
     "axios": "^1.7.7",
     "chalk": "^5.3.0",
     "debug": "^4.3.7",
-    "jsonpathly": "^2.0.2",
+    "jsonpathly": "^3.0.0",
     "mergician": "^2.0.2",
     "open": "^10.1.0"
   }

package.json

@@ -90,8 +90,11 @@ export class Overlay {
     // The last element (e.g. '"price"]' or '0]') contains a final ']'
     // so we need to remove it AND we need to parse the element to
     // transform the string in either a string or a number
+    // Note: since jsonpathly v3, the returned JSON Path is wrapped in single quotes, which requires manual handling
     thingToActUpon =
-      thingToActUpon === undefined ? '$' : (thingToActUpon = JSON.parse(thingToActUpon.slice(0, -1)) as number | string)
+      thingToActUpon === undefined
+        ? '$'
+        : (thingToActUpon = JSON.parse(thingToActUpon.slice(0, -1).replaceAll("'", '"')) as number | string)
 
     // Reconstruct the stringified path expression targeting the parent
     const parentPath: string = explodedPath.join('][')