[rush] Add support for PNPM version 3.x

[tnc1997]

This pull request follows on from issues #1145 and #1180 and adds preliminary support for pnpm version 3.

The --resolution-strategy flag has been added to the pnpmOptions section of rush.json and both of the different filenames given to the pnpm 'lock' files based on the pnpm version are supported.

[msftclas]

All CLA requirements met.

[octogonz]

@iclanton I tested this over the weekend, and it's in good shape, but I found that PNPM 3.0.0 fails if the new option is provided. I was working on a fix for that yesterday but got distracted. I can finish it tonight.

[iclanton]

AWS

[iclanton]

Drop the "number" at the end of this sentence.

[iclanton]

It kinda feels like this data should be expressed in JSON files. TS for code, JSON for data.

[octogonz]

Maybe, but let's collect a little more "data" before we design a specialized manager for it

[iclanton]

Sure - that's fine.

[octogonz]

This PR was published with Rush 5.7.0

[octogonz]

In PR #1244 the build is failing with this error:

ERROR: Invalid Version: 1.0.3_@pnpm+logger@1.0.2

TypeError: Invalid Version: 1.0.3_@pnpm+logger@1.0.2
    at new SemVer (C:\Users\Owner\.rush\node-v10.15.2\rush-5.7.0\node_modules\semver\semver.js:293:11)
    at Range.test (C:\Users\Owner\.rush\node-v10.15.2\rush-5.7.0\node_modules\semver\semver.js:1036:15)
    at Function.satisfies (C:\Users\Owner\.rush\node-v10.15.2\rush-5.7.0\node_modules\semver\semver.js:1085:16)
    at PnpmShrinkwrapFile.checkValidVersionRange

It seems the shrinkwrap.yaml changed from this:

'file:projects/rush-lib.tgz':
    dependencies:
      '@pnpm/link-bins': /@pnpm/link-bins/1.0.3/@pnpm!logger@1.0.2

...to this in the new pnpm-lockfile.json:

  'file:projects/rush-lib.tgz':
    dependencies:
      '@pnpm/link-bins': 1.0.3_@pnpm+logger@1.0.2

@tnc1997 @bsiegel did you encounter this? Maybe we need to update the version parsing in PnpmShrinkwrapFile.ts

[tnc1997]

Hi @octogonz, I've just checked out all of the latest changes and I can confirm that I too am getting the same error. As you mention, it seems to point towards a change in how version numbers are represented in the latest version of pnpm, which might require a modification to the version parsing used.

[octogonz]

I'm going to see if I can debug it tonight

[octogonz]

Okay, I have a fix. I'll create a PR later tonight.

[octogonz]

Here's the PR: #1246