Make TerminalOutput.pathToMaven() more robust to avoid #929

[ppalaga]

Mitigates #929 but does not have an ambition to find the root cause.

[gastaldi]

It would be nice to log (debug?) when the URL is malformed

[ppalaga]

It would be nice to log (debug?) when the URL is malformed

Well, the issue we are mitigating happens only in the text UI, where the place is sparse and where there is no concept of log level. I am not sure the information that we were not able to parse some URL is that interesting to end users. If we cannot parse it, we just print it as is. If the transfer failure matters, the daemon will inform them through a separate message. If it is ignorable, I do not think they need to know. My 2c.

[gnodet]

LGTM. Next maven resolver will probably have a better way to access this information with apache/maven-resolver#474, so we'll be able to update to that one when it's integrated into 3.9.x and 4.x maven branches.