test: cover encoded UTF-8 URI resolution

[Poliklot]

Summary

• add regression coverage for #157, ensuring resolve() retains UTF-8 percent-encoded path segments instead of producing legacy unescape()-style Latin-1 output;
• cover the corresponding JSON Schema reference fixture from sagold/json-schema-library#82, where uri-js had been used as a workaround;
• lock in the current implementation's correct behaviour without adding a dependency or changing public API.

The commit credits the original report and fixture research:

Co-authored-by: Dmitry Arkhipov <2089893+ekzobrain@users.noreply.github.com>

Closes #157.

Validation

• npm test
• npm run lint
• npm run test:typescript
• npm run test:browser:chromium

[mcollina]

lgtm

[mcollina]

I'm sorry but I don't understand this, how can we close that issue with just a test?

[Poliklot]

@mcollina You’re absolutely right: this PR only adds regression coverage; it does not implement the functional fix.

I verified that the reported reproducer returns http://host/�� in v3.1.0, while v3.1.1 returns the correct http://host/%D1%8B%D1%8B. The underlying fix had already landed in 876ce79, which replaces the unescape() path handling with percent-encoding normalization.

So Closes #157 is misleading here: #200 should only reference the issue, while #157 can be closed separately as already fixed. Thanks for catching this.