deps: upgrade npm to 8.19.1

deps/npm/docs/content/commands/npm-install.md

@@ -79,7 +79,7 @@ into a tarball (b).
     If `<folder>` sits inside the root of your project, its dependencies will be installed and may
     be hoisted to the top-level `node_modules` as they would for other
     types of dependencies. If `<folder>` sits outside the root of your project,
-    *npm will not install the package dependencies* in the directory `<folder>`,
+    *npm will not install the package dependencies* in the directory `<folder>`, 
     but it will create a symlink to `<folder>`.
 
     > NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use the `--install-links` option.

deps/npm/docs/content/commands/npm-query.md

@@ -233,3 +233,4 @@ This value is not exported to the environment for child processes.
 ## See Also
 
 * [dependency selectors](/using-npm/dependency-selectors)
+

deps/npm/docs/content/configuring-npm/package-lock-json.md

@@ -36,7 +36,7 @@ various purposes:
 Both of these files have the same format, and perform similar functions in
 the root of a project.
 
-The difference is that `package-lock.json` cannot be published, and it will
+The difference is that `package-lock.json` cannot be published, and it will 
 be ignored if found in any place other than the root project.
 
 In contrast, [npm-shrinkwrap.json](/configuring-npm/npm-shrinkwrap-json) allows

deps/npm/docs/content/using-npm/scope.md

@@ -87,8 +87,8 @@ Publishing to a scope, you have two options:
 If publishing a public module to an organization scope, you must
 first either create an organization with the name of the scope
 that you'd like to publish to or be added to an existing organization
-with the appropriate permisssions. For example, if you'd like to
-publish to `@org`, you would  need to create the `org` organization
+with the appropriate permisssions. For example, if you'd like to 
+publish to `@org`, you would  need to create the `org` organization 
 on npmjs.com prior to trying to publish.
 
 Scoped packages are not public by default.  You will need to specify

deps/npm/docs/content/using-npm/scripts.md

@@ -219,7 +219,7 @@ will default the `start` command to `node server.js`.  `prestart` and
 
 #### A Note on a lack of [`npm uninstall`](/commands/npm-uninstall) scripts
 
-While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful.
+While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful. 
 
 Reasons for a package removal include:
 

deps/npm/man/man1/npm-install.1

@@ -79,7 +79,7 @@ NOTE: The \fB\-\-production\fP flag has no particular meaning when adding a
   If \fB<folder>\fP sits inside the root of your project, its dependencies will be installed and may
   be hoisted to the top\-level \fBnode_modules\fP as they would for other
   types of dependencies\. If \fB<folder>\fP sits outside the root of your project,
-  \fInpm will not install the package dependencies\fR in the directory \fB<folder>\fP,
+  \fInpm will not install the package dependencies\fR in the directory \fB<folder>\fP, 
   but it will create a symlink to \fB<folder>\fP\|\.
 .QP
 NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use the \fB\-\-install\-links\fP option\.

deps/npm/man/man5/package-lock-json.5

@@ -35,7 +35,7 @@ files, and allowing for significant performance improvements\.
 Both of these files have the same format, and perform similar functions in
 the root of a project\.
 .P
-The difference is that \fBpackage\-lock\.json\fP cannot be published, and it will
+The difference is that \fBpackage\-lock\.json\fP cannot be published, and it will 
 be ignored if found in any place other than the root project\.
 .P
 In contrast, npm help npm\-shrinkwrap\.json allows

deps/npm/man/man7/scope.7

@@ -92,8 +92,8 @@ Publishing to an organization scope (example: \fB@org/module\fP)
 If publishing a public module to an organization scope, you must
 first either create an organization with the name of the scope
 that you'd like to publish to or be added to an existing organization
-with the appropriate permisssions\. For example, if you'd like to
-publish to \fB@org\fP, you would  need to create the \fBorg\fP organization
+with the appropriate permisssions\. For example, if you'd like to 
+publish to \fB@org\fP, you would  need to create the \fBorg\fP organization 
 on npmjs\.com prior to trying to publish\.
 .P
 Scoped packages are not public by default\.  You will need to specify

deps/npm/man/man7/scripts.7

@@ -314,7 +314,7 @@ will default the \fBstart\fP command to \fBnode server\.js\fP\|\.  \fBprestart\f
 .RE
 .SS A Note on a lack of npm help \fBuninstall\fP scripts
 .P
-While npm v6 had \fBuninstall\fP lifecycle scripts, npm v7 does not\. Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful\.
+While npm v6 had \fBuninstall\fP lifecycle scripts, npm v7 does not\. Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful\. 
 .P
 Reasons for a package removal include:
 .RS 0