fix: change npm profile to create tokens with GAT support

[owlstronaut]

This pull request introduces extensive enhancements to the npm token management command, adding support for creating Granular Access Tokens (GATs) with fine-grained permissions. It updates the CLI interface, configuration, and documentation to allow users to specify token details such as name, description, expiration, package/scope/org restrictions, permission levels, and bypassing two-factor authentication. The changes also improve error messaging and ensure all new options are reflected in the config and docs.

Needs npm/npm-profile#175 changes/release before this will work.

[wraithgar]

I think we may want to namespace a few of these to gat-, if not all of them.

[wraithgar]

Updated to just use npm-registry-fetch. Tests still need updating.

[cs5vsm99xq-wq]

This pull request introduces extensive enhancements to the npm token management command, adding support for creating Granular Access Tokens (GATs) with fine-grained permissions. It updates the CLI interface, configuration, and documentation to allow users to specify token details such as name, description, expiration, package/scope/org restrictions, permission levels, and bypassing two-factor authentication. The changes also improve error messaging and ensure all new options are reflected in the config and docs.

Needs npm/npm-profile#175 changes/release before this will work.