feat: hardware security module's support

[DanielHougaard]

Description 📣

This PR introduces hardware security module's support. It works as wrapper around any PKCS11 library, and allows for more secure cryptographic operations such as encryption, decryption, and randomness generation.

The implementation uses a key-wrapping mechanism, so it never directly uses the HSM primary encryption key.

Currently it supports recovery, but we need to iron out if this is actually behavior we want to allow. cc @maidul98

Type ✨

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[akhilmhdh]

Pending: Application testing and need to read about HSM slot mechanism more

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14456465	Triggered	Generic High Entropy Secret	395b3d9	backend/src/ee/services/hsm/hsm-service.ts	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}