feat(fips): native FIPS support

[DanielHougaard]

Description 📣

Native FIPS support

This PR introduces FIPS validation support (enterprise-only) for plain Infisical installations. There is no way to migrate from non-FIPS -> FIPS, so things doesn't need to be backwards compatible with each other.

Core changes:

1. We've bundled in OpenSSL 3.1.2 which is FIPS validated, and we've toggled on FIPS mode for it
2. We are forcing FIPS mode Node.js during startup. This means that Node.js won't allow OpenSSL to execute non-fips validated algorithms
3. Introduced crypto.js usage. This is only intended to be used in cases where we absolutely have to use non-fips validated algorithms. We use their md5 implementation for MongoDB digest auth for our dynamic secrets.
4. We're moved all crypto usage into a crypto provider (cryptographyFactory), which will handle all exports of crypto. This way we can be very explicit about what crypto we are using.
5. TweetNacl has been replaced with native node crypto. We replicate tweetnacl's asymmetric key-sharing encryption by using the Diffie-Hellman key exchange algorithm; which is implemented in native node.
6. jsonwebtoken is replaced with our own JWT implementation using native Node.
7. BCrypt has been replaced with pkdf2. We enforce a minimum of 1.000.000 iterations to keep the compute intensity high to avoid brute-force attacks.

To test things out, you can run make up-dev. Development node will now always run in FIPS-mode to ensure that we aren't developing features that won't be compatible with FIPS.

Type ✨

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

---

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

[maidul98]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[DanielHougaard]

Merging at a later time as this is high-impact

[maidul98]

implementation looks good, just left some minor comments