This fixes a ERR_INVALID_OPT_VALUE error on Node v12

Several changes to the test suite to support running tests in parallel,
bringing the overall test time down considerably.

- Replace all literal 1337 and 1234 ports with a custom per-process port
  assignment based on the TAP_CHILD_ID environment variable.
- Add common.pkg as a per-test working directory instead of polluting
  __dirname or accidentally reusing the same working directory for
  multiple tests.
- Rework test config handling so that tests don't rely on config setup
  being run in a particular order.
- Remove the npm-registry-couchapp tests, since it (a) relies on
  CouchDB, (b) is no longer a reliable indicator of registry
  compatibility, and (c) is already superceded in most cases by tests
  that use npm-registry-mock.  (A test suite that runs against a
  reference implementation is a thing that should exist, but not here.)
- Remove the fake-registry logging when TAP_CHILD_ID is set, since this
  is extremely hard to make sense of when running multiple tests in
  parallel.

When Node v6 compatibility is dropped in npm v7, we can upgrade to the
latest version of tap for a bit more speed, dropping Domains (and the
associated deprecation warnings), and a fancier test reporter.

Add a special case for 'remote' deps (tarballs). Before
b7b54f2 the package names were possibly
just looked up in the registry instead.

See https://npm.community/t/6187

Close: #180

Close: #183

-a tells git to "ignore the git config for signing tags"

that is all it does.

Close: #185

Note: SemVer minor -- @isaacs

implementation added in #31

I spent a couple hours debugging the fact that package names in that key aren't supposed to include their versions!  Assumed that it would need to have the same syntax as when running `npm install`.  Thought this would be a good contribution for future readers.

Signed-off-by: ossdev <ossdev@puresoftware.com>

Addresses https://www.npmjs.com/advisories/886

npm find local node.exe on windows, but relies on global node
installation on linux. Added a test to check for a local installation of
node before relying on the system wide installation.

Close: #200

Note: SemVer minor -- @isaacs

Close: #202

Never include /.git in the package.  It creates packages that, once
installed, can not be easily removed.

Prevent .DS_Store files from being picked up if they are files rather
than folders.  (Note that a .DS_Store file in a specifically included
dir _will_ still be included.)

Don't bother walking node_modules in the root if no packages are
bundled.  (Saves thousands of lstat calls on npm publish in normal
cases.)

Sort package file lists in the tarball to optimize for gzip compression.

Fixes a bug related to FSReqWrap on Node v12, and incorrect
encoding/decoding of base-256 numeric values.

Fix: npm/npm#17858
Fix: npm/npm#18042
Fix: https://npm.community/t/issue-npm-dedupe-crash-with-typeerror-cannot-read-property-0-of-undefined/644/3
Close: #201

This fixes a bug where a package folder might have a package.json which
is missing or lacks a name property.  It also properly detects the
scoped-ness of a package folder even if the package name is not scoped,
since one might install `express@npm:@scope/express` and end up in that
state.

Close: #176

EDIT: Added test, do not set exitStatus to 1 if we're just printing an
empty list as JSON. -- @isaacs

Total luxury problem.  There are too many cores on my laptop, so
commands kick off and complete too quickly, resulting in not properly
demonstrating the behavior that this test is looking for.

Missed this on the review.  Minor nit, not worth rebasing, now that the
release is almost ready to ship.