chore: check less stuff into node_modules

We bundle our deps, but we don't need to bundle docs, changelogs,
editorconfigs, test coverage reports, .github workflow definitions,
lint configurations, and all the rest, which we never use.

This cuts about 10% off of our publish artifact file size.

```
$ ls -laF npm-7.16.0-*.tgz
-rw-r--r--  1 isaacs  staff  7174497 Jun  3 13:01 npm-7.16.0-release-next.tgz
-rw-r--r--  1 isaacs  staff  6782377 Jun  3 13:00 npm-7.16.0-trim-node-modules.tgz

$ ls -laF npm-7.16.0-*.tar
-rw-r--r--  1 isaacs  staff  19020288 Jun  3 13:01 npm-7.16.0-release-next.tar
-rw-r--r--  1 isaacs  staff  17474048 Jun  3 13:00 npm-7.16.0-trim-node-modules.tar
```

PR-URL: https://github.com/npm/cli/pull/3362
Credit: @isaacs
Close: #3362
Reviewed-by: @nlf

2 files changed, 0 insertions, 66 deletions

diff --git a/node_modules/init-package-json/CHANGELOG.md b/node_modules/init-package-json/CHANGELOG.md
deleted file mode 100644
index 92e92aed1..000000000
--- a/node_modules/init-package-json/CHANGELOG.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Change Log
-
-<a name="2.0.0"></a>
-## [2.0.0](https://github.com/npm/init-package-json/compare/v1.10.3...v2.0.0) (2020-10-09)
-* BREAKING: requires node10+
-* fix: compat with new `@npmcli/config` module
-* chore: update deps to latest and greatest
-
-<a name="1.10.3"></a>
-## [1.10.3](https://github.com/npm/init-package-json/compare/v1.10.2...v1.10.3) (2018-03-07)
-
-
-
-<a name="1.10.2"></a>
-## [1.10.2](https://github.com/npm/init-package-json/compare/v1.10.1...v1.10.2) (2018-03-07)
-
-
-### Bug Fixes
-
-* **default-input:** Catch errors from npa ([#71](https://github.com/npm/init-package-json/issues/71)) ([11aee1e](https://github.com/npm/init-package-json/commit/11aee1e))
-* **grammar:** Fix minor style issue in final prompt ([#76](https://github.com/npm/init-package-json/issues/76)) ([ba259ce](https://github.com/npm/init-package-json/commit/ba259ce))
diff --git a/node_modules/init-package-json/README.md b/node_modules/init-package-json/README.md
deleted file mode 100644
index 528acf355..000000000
--- a/node_modules/init-package-json/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# init-package-json
-
-A node module to get your node module started.
-
-[![Build Status](https://secure.travis-ci.org/npm/init-package-json.svg)](http://travis-ci.org/npm/init-package-json)
-
-## Usage
-
-```javascript
-var init = require('init-package-json')
-var path = require('path')
-
-// a path to a promzard module.  In the event that this file is
-// not found, one will be provided for you.
-var initFile = path.resolve(process.env.HOME, '.npm-init')
-
-// the dir where we're doin stuff.
-var dir = process.cwd()
-
-// extra stuff that gets put into the PromZard module's context.
-// In npm, this is the resolved config object.  Exposed as 'config'
-// Optional.
-var configData = { some: 'extra stuff' }
-
-// Any existing stuff from the package.json file is also exposed in the
-// PromZard module as the `package` object.  There will also be three
-// vars for:
-// * `filename` path to the package.json file
-// * `basename` the tip of the package dir
-// * `dirname` the parent of the package dir
-
-init(dir, initFile, configData, function (er, data) {
-  // the data's already been written to {dir}/package.json
-  // now you can do stuff with it
-})
-```
-
-Or from the command line:
-
-```
-$ npm-init
-```
-
-See [PromZard](https://github.com/npm/promzard) for details about
-what can go in the config file.