fix: recursion detection to allow same resolved $ref in different branches

[catosaurusrex2003]

The Problem

The recursion detection algorithm incorrectly throws "too much recursion" errors when the same external $ref appears in multiple branches (e.g. in the schema provided in #1236 c1 and c2 both referencing the same external component).

This happens because the algorithm used a global WeakSet that flagged any object seen before, even if it was in a different branch.

Solution

Replaced global WeakSet tracking with path-based tracking using Set<object>. Each branch now gets its own copy of the path, allowing the same object to appear in different branches while still detecting true circular references.

Key Changes

• Changed WeakSet → Set<object> to enable path copying
• Renamed visited → visitedInPath for clarity
• Create new path copy for each branch instead of sharing global set

Related issue(s)

#1236

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud