deps: upgrade npm to 8.19.3

PR-URL: #45322
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

Author: npm-cli-bot

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

@@ -6,10 +6,6 @@ description: Set access level on published packages
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/access.js -->
-
 ```bash
 npm access public [<package>]
 npm access restricted [<package>]
@@ -22,11 +18,6 @@ npm access ls-collaborators [<package> [<user>]]
 npm access edit [<package>]
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/access.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 ### Description
 
 Used to set access controls on private packages.
@@ -88,19 +79,13 @@ Management of teams and team memberships is done with the `npm team` command.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `otp`
 
 * Default: null
@@ -112,11 +97,6 @@ when publishing or changing package permissions with `npm access`.
 If not set, and a registry response fails with a challenge for a one-time
 password, npm will prompt on the command line for one.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [`libnpmaccess`](https://npm.im/libnpmaccess)

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

@@ -6,21 +6,12 @@ description: Add a registry user account
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/adduser.js -->
-
 ```bash
 npm adduser
 
 aliases: login, add-user
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/adduser.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 Note: This command is unaware of workspaces.
 
 ### Description
@@ -44,19 +35,13 @@ your existing record.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `scope`
 
 * Default: the scope of the current project, if any, or ""
@@ -87,9 +72,6 @@ npm init --scope=@foo --yes
 ```
 
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `auth-type`
 
 * Default: "legacy"
@@ -100,11 +82,6 @@ removed in a future version.
 
 What authentication strategy to use with `login`.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [npm registry](/using-npm/registry)