Update registry documentation to reflect that Granular Access Tokens can now
be configured to bypass 2FA requirements, making them the recommended modern
alternative to legacy automation tokens for CI/CD workflows.

Changes:
- Updated about-access-tokens.mdx to emphasize GATs as superior alternative
  to automation tokens with enhanced security features
- Added bypass 2FA configuration step to creating-and-viewing-access-tokens.mdx
- Updated CI/CD workflow documentation to recommend GATs with bypass 2FA
- Clarified package publishing 2FA requirements for tokens configured to bypass 2FA
- Added comprehensive note in about-two-factor-authentication.mdx explaining
  GAT bypass capability and its advantages

Note: CLI files (content/cli/**) are not modified as they are sourced from
npm/cli repository and will be updated in a future npm release.

- Updated step 9 to use 'useful' instead of 'ideal' for CI/CD workflows
- Clarified that unchecked means token respects account's normal 2FA settings
- Removed security warning note per decision to keep documentation straightforward

- Add description of bypass 2FA column in token list (shows checkmark for GATs with bypass enabled)
- Add instructions for viewing full GAT details including bypass 2FA configuration
- Add web interface method for token revocation (previously only documented CLI)
- Clarify that all token types including GATs with bypass 2FA can be revoked

…on tokens

- Update all GAT bypass 2FA mentions to emphasize it's the modern replacement for legacy automation tokens
- Add deprecation notices where GAT bypass 2FA is discussed
- Clarify that legacy automation tokens are being deprecated
- Updated files:
  - about-two-factor-authentication.mdx
  - about-access-tokens.mdx
  - creating-and-viewing-access-tokens.mdx
  - using-private-packages-in-a-ci-cd-workflow.mdx
  - requiring-2fa-for-package-publishing-and-settings-modification.mdx