feat: add property forceMigrateToSecureLegacySignature

[juanpicado]

• reuse code from @verdaccio/auth and clean up duplicated code
• follow up of feat: add migrateToSecureLegacySignature property #4621 implement forceMigrateToSecureLegacySignature and autoupgrade
• breaking change for users that uses old secret token (64 characters length) and Node.js 22

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
7921693	Triggered	Generic High Entropy Secret	460e116	test/unit/partials/mock-store/.sinopia-db.json	View secret
10612671	Triggered	Generic High Entropy Secret	460e116	test/unit/partials/mock-store/.sinopia-db.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}