feat(core): crypto compatibility for Workers

[vejja]

Resolves #541

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

This PR replaces the NodeJS cryptographic primitives used in this codebase by their equivalents from the Javascript WebCrypto API.

The fundamental reason for this rewrite is to provide full compatibility with Worker-based environments, where Node's crypto module might not always be available.

The issue was first raised with Cloudflare's Workers. While manual configuration of Cloudflare worker settings (via their nodejs_compatibility flag) is possible, we believe it is better to offer a universal approach that will offer strong cryptographic guarantees in all environments.

Note: as part of this update, the NodeJS minimal version needs to be updated to v20. This is required to ensure that crypto is available in the global scope.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nuxt-security	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 11, 2024 5:35pm

[vejja]

@Baroshem for some reason I had troubles rebasing the branch onto 2.1.0 - sorrry the commit timeline looks awful, but actually the amount of changes is very small

[Baroshem]

Nice job @vejja !

No worries about the commit history. Glad you have managed to make it work. Proceed with merging when you feel ready. @brewwa would you be able to test this branch? :)

[vejja]

Hey Jakub, I tested it on a private repo that @brewaa provided, and it works on Cloudflare. Will merge