Verify version when resolving Node builtin polyfills

[mischnic]

This will call packageManager.resolve for every resolution of a Node builtin with the correct range that should be used to catch cases where another instance of some Node builtin polyfill was pulled in by some other dependency, be it in the same package, or in a monorepo situation

If it's the wrong version, it will either autoinstall, or error (using the existing autoinstall logic):

@parcel/core: Failed to resolve 'util' from './a/index.js'
  /Users/nmischkulnig/Desktop/monorepo-builtin-versioning/a/index.js:1:20
  > 1 | import * as x from "util";
  >   |                    ^^^^^^
    2 |
    3 | console.log(x);


@parcel/package-manager: Could not find module "util" satisfying ^0.12.3.

  /Users/nmischkulnig/Desktop/monorepo-builtin-versioning/a/package.json:6:3
    5 |   "dependencies": {
  > 6 |     "util": "^0.4.9"
  >   |     ^^^^^^ Found this conflicting local requirement.
    7 |   }
    8 | }

Questions:

• Previously, the polyfill was resolved from the actual source file but autoinstalled into the project root. We either need to install it into the local package (what I've done now), or resolve it relative from the monorepo root. (So that resolution base = autoinstall target) Now, all builtin polyfills are resolved from the project root
• Is it a concern that packageManager.resolve is slow? I suspect there won't be that many Node builtins anyway

[mischnic]

The url polyfill package declares punycode as a dependency

https://github.com/defunctzombie/node-url/blob/5480ec001102457ac00c3c7878facdec39b536c8/package.json#L6-L9

but then does require("punycode") which uses the node polyfill (as opposed to require("punycode/")). I needed to declare this version to get the integration tests to pass....