[System] Test Uri constructor with escaped user info chars.
[System] Fixed UriParseComponents.ParseUser. Fixes #25087.
UriParseComponents.ParseUser was unescaping all escaped chars and when a non valid user info char was encountered it was assuming that those chars were not part of the user info. The chars were not consumed thus the problems while parsing the rest of the input.
UriParseComponents.ParseUser now keeps non valid user info chars escaped.
Merge pull request #1443 from esdrubal/userinfoescape

[System] Fixed UriParseComponents.ParseUser.