fix(deps): update dependency normalize-url to ^2.0.0

[renovate]

This Pull Request updates dependency normalize-url from ^1.9.1 to ^2.0.0

Commits

v2.0.0

• 48b1864 ES2015ify and require Node.js 4
• b125e29 Add a sortQueryParameters option (#​48)
• 28a8383 Meta tweaks
• 665eb4b Bump dependencies
• 3e99387 2.0.0

v2.0.1

• 01fc811 Avoid appending a 'null' string as query params (#​54)
• f4df606 2.0.1

---

This PR has been generated by Renovate Bot.

[buildsize]

This change will increase the build size from 10.49 MB to 10.5 MB, an increase of 8.09 KB (0%)

File name	Previous Size	New Size	Change
yarn-[version].noarch.rpm	909.34 KB	910.04 KB	719 bytes (0%)
yarn-[version].js	3.95 MB	3.96 MB	2.97 KB (0%)
yarn-legacy-[version].js	4.1 MB	4.1 MB	2.97 KB (0%)
yarn-v[version].tar.gz	914.8 KB	915.66 KB	882 bytes (0%)
yarn_[version]all.deb	675.21 KB	675.79 KB	596 bytes (0%)

[rarkins]

Possibly an ephemeral failure?

Summary of all failing tests
FAIL __tests__\package-resolver.js (99.946s)
  ● resolve git+https://github.com/ocaml/ocaml.git#4.02.3
    Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
      
      at node_modules/jest-jasmine2/build/queue_runner.js:64:21
      at Timer.listOnTimeout (timers.js:92:15)

The only suspicious thing was that it's node.js 4

[Simek]

I was getting random timeouts when I was reverting those test to live so timeout has beed extended by 30s (#5165) . Same situation as here happend in #5184, but on Node 8. Those timeout issues are really weird and inconsistent.

Max resolve time seems peak across few dependencies bump PRs was around 130s. As a temporal solution we could extend Jasmine timeout even more, but this will be only a workaround.

Also maybe changing OCaml to other smaller repo i.e. Yarn/Lodash will be better approach?