fix: fragment encoding

[zekth]

[Draft]
currently having issue with fragment encoding like:

• #/$defs/stringMap
• #/$defs/string%20Map

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[Eomm]

I miss the escape usage.
There is any reason to prefer it over encodeURI and decodeURI?

This fix could impact the performance.. need to try it

[zekth]

Iirc i switched to escape because it was faster. I'll have to run some benchmarks. But at the moment i switched i cleaned up a lot the parse flow. Going to check

[mcollina]

lgtm

[zekth]

@mcollina @Eomm using encode/decode is not impacting that much, still a bit but not crazy high overhead. I'd land this as a patch and we can take care of the whole encoding flow issue in another PR.
Sorry when i refactored it i might have missed some spots and got lost at some point.