[npm-registry-fetch] Add authType field to AuthOptions

[arayaryoma]

The authType option is used as npm-auth-type request header field. ref:

• https://github.com/npm/npm-registry-fetch/blob/ceaf77ece4eb71a4ab1f9542bf4e75aec0dd4b05/lib/index.js#L218-L220
• https://docs.npmjs.com/cli/v10/commands/npm-login

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change.
• Follow the advice from the readme.
• Avoid common mistakes.
• Run pnpm test <package to test>.

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: <https://github.com/npm/npm-registry-fetch/blob/ceaf77ece4eb71a4ab1f9542bf4e75aec0dd4b05/lib/index.js#L218-L220>
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the package.json.

[typescript-bot]

@arayaryoma Thank you for submitting this PR!

This is a live comment which I will keep updated.

1 package in this PR

• npm-registry-fetch — on npm, on unpkg

Code Reviews

Because you edited one package and updated the tests (👏), I can help you merge this PR once someone else signs off on it.

You can test the changes of this PR in the Playground.

Status

• ✅ No merge conflicts
• ✅ Continuous integration tests have passed
• ✅ Most recent commit is approved by type definition owners, DT maintainers or others

All of the items on the list are green. To merge, you need to post a comment including the string "Ready to merge" to bring in your changes.

Inactive

This PR has been inactive for 19 days — please merge or say something if there's a problem, otherwise it will be closed!

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 69478,
  "author": "arayaryoma",
  "headCommitOid": "6063c40c269013b5c2601ba7eea29c958542ff4c",
  "mergeBaseOid": "778ad7a80e9876f258270d84d1db4e6e1d5e3796",
  "lastPushDate": "2024-04-30T15:59:25.000Z",
  "lastActivityDate": "2024-05-05T06:58:01.000Z",
  "mergeOfferDate": "2024-05-05T06:58:39.000Z",
  "hasMergeConflict": false,
  "isFirstContribution": false,
  "tooManyFiles": false,
  "hugeChange": false,
  "popularityLevel": "Well-liked by everyone",
  "pkgInfo": [
    {
      "name": "npm-registry-fetch",
      "kind": "edit",
      "files": [
        {
          "path": "types/npm-registry-fetch/index.d.ts",
          "kind": "definition"
        },
        {
          "path": "types/npm-registry-fetch/npm-registry-fetch-tests.ts",
          "kind": "test"
        }
      ],
      "owners": [],
      "addedOwners": [],
      "deletedOwners": [],
      "popularityLevel": "Well-liked by everyone"
    }
  ],
  "reviews": [
    {
      "type": "approved",
      "reviewer": "Anonymous4078",
      "date": "2024-05-05T06:58:01.000Z",
      "isMaintainer": false
    }
  ],
  "mainBotCommentID": 2085778673,
  "ciResult": "pass"
}

[typescript-bot]

🔔 @arayaryoma — there are no owners, but it would still be good if you find someone to review this PR in the next few days, otherwise a maintainer will look at it. (And if you do find someone, maybe even recruit them to be a second owner to make future changes easier...)

[typescript-bot]

@arayaryoma: Everything looks good here. I am ready to merge this PR (at 6063c40) on your behalf whenever you think it's ready.

If you'd like that to happen, please post a comment saying:

Ready to merge

and I'll merge this PR almost instantly. Thanks for helping out! ❤️

[typescript-bot]

Re-ping @arayaryoma / @«anyone?»:

This PR has been ready to merge for over a week, and I haven't seen any requests to merge it. I will close it on Jun 4th (in three weeks) if this doesn't happen.

(If there's no reason to avoid merging it, please do so. Otherwise, if it shouldn't be merged or if it needs more time, please close it or turn it into a draft.)