fix: sanitize() double encode special characters

[stepashka69]

Description

Use URL().toString() to construct sanitised URI (including support of IP v6 URIs).
Fall back to the existent functionality in cases when URL() can not parse the URI.

Motivation and Context

The problem is described in #3270 .
Existent sanitize implementation doesn't return correct result when the URI contains encoded 'special' characters such as ; / ? : @ & = + $ , #.
Closes #3270

How Has This Been Tested?

Tested with existent unit tests.
Extended test for the case with special characters and added test case for IP v6.

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[char0n]

Hi @stepashka69,

Thanks for the PR! I'll process it ASAP and release the bugfix.

[char0n]

@stepashka69 looks good. There is additional unsanitize function, which needs to be aligned with the sanitized function now.

UPDATE:

decodeURI is currently not replaceable by URL (in it's current implementation). So we leave unsanitize untouched.

The URL interface is used to parse, construct, normalize, and encode URLs.

URLs are encoded according to the rules found in RFC 3986

[char0n]

Nicely done!