url: runtime deprecate legacy api

[jasnell]

This might be a bit controversial. The legacy url.parse()/url.format()/url.resolve() API has been runtime deprecated for a few years now and developers really should be using the URL object instead. It's time we elevated to a runtime deprecation to more actively discourage use of the old API.

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• documentation is changed or added
• commit message follows commit guidelines

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/32924/

[lpinca]

I think this will create a lot of unnecessary "panic" in user land.

[devsnek]

I'm a fan of this but this is probably going to warn on every bit of code ever written, we might need to filter out node_modules like the buffer runtime deprecation.

[lpinca]

Another problem is that it is not trivial to migrate to URL. Some examples:

• I have legacy code that expects uri.query to be a plain object as returned by const uri = url.parse(string, true). To do the same with URL is it necessary to convert url.searchParams (a URLSearchParams instance) to a plain object or parse url.search again which results in a significant drop of performance.
• There is no replacement url.format() (WhatWG URL provides no suitable replacement for url.format() #25099).

[jasnell]

Ok. Will close this for now and revisit later.