fix(evaluate): make <= and >= yield true when both operands are Nothing

[char0n]

Fixes #144

Problem

When both operands of a comparison resolve to Nothing (for example two absent members), == selected the node but <= and >= did not:

evaluate([{}], '$[?@.a == @.b]'); // [{}]
evaluate([{}], '$[?@.a <= @.b]'); // []   expected [{}]
evaluate([{}], '$[?@.a >= @.b]'); // []   expected [{}]

RFC 9535 §2.3.5.2.2 defines the non-strict operators by composition: a <= b is true iff a < b or a == b, and a >= b is true iff b < a or a == b. Since Nothing == Nothing is true, both non-strict comparisons must hold. The RFC's own example table in §2.3.5.3 lists $.absent1 <= $.absent2 as true with the comment "== implies <=".

Cause

JSONEvaluationRealm.compare() returned false early from the <= and >= branches whenever either side was Nothing, before reaching the deep equality fallback at the end of each branch.

Fix

Remove the early return from the <= and >= branches only. The number and string checks don't match undefined, so the branch falls through to deep equality, which already returns true for Nothing vs Nothing and false for Nothing vs a value. Strict < and > are unchanged and still reject Nothing.

Why the compliance suite didn't catch it

Every <=/>= test in the JSONPath Compliance Test Suite compares members that both exist, and the Nothing-related tests only use ==/!=. The RFC §2.3.5.3 example table was never transcribed into the suite. A new test/evaluate/comparison.js covers all six operators with Nothing on both sides and on one side only.

Verification

• Reporter's reproduction now returns [{}] for ==, <=, >= and [] for !=, <, >.
• All five absent-member rows of the RFC §2.3.5.3 table now match.
• Full suite passes (1314 tests, compliance suite included).

[char0n]

🎉 This PR is included in version 4.0.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀