feat(crypto)!: libsodium crypto implementation

[AngelCastilloB]

Context

Currently, the SDK uses the Cardano Multiplatform Lib to perform all Ed25519-related operations. We want to replace this dependency by implementing our own package that uses libsodium for cryptographic operations.

Proposed Solution

Introduce a new set of ed25519 classes to the crypto package based on libsodium. There is also a new BIP32 set of classes implemented natively in javascript for key public and private key derivation.

Critical Segments

This PR introduces some code that must be audited and verified, as we consider it to be critical:

• BIP-32 key derivation: The core logic that does the derivation is contained in this ts file Bip32KeyDerivation.ts , and the following classes are implemented in terms of the functions defined in such file: Bip32PrivateKey.ts and Bip32PublicKey.ts
• Ed25519 Extended: Libsodium doesn't support out-of-the-box extended keys in its high-level API (crypto_sign and crypto_sign_detached), so we had to implement our own sign method using the Ed25519 primitives provided by the libsodium library, said function can be found here: signExtendedDetached, the following classes will be also a point of interest for reviewers: Ed25519PrivateKey.ts and Ed25519PublicKey.ts

Important Changes Introduced

• A new set of classes were introduced to the 'crypto' package, which contains several classes and utilities to perform Ed25519 cryptographic operations using libsodium.
• Added a new implementation of the Bip32Ed25519 interface.
• Unit tests and e2e test now uses the new SodiumBip32Ed25519 concrete class by default.

[rhyslbw]

Fantastic work here @AngelCastilloB

[iquerejeta]

First round of comments.

[mkazlauskas]

Some additional refactoring is needed:

• typedHex() should probably live in util package just like opaqueTypes (seems to be duplicated in core & crypto packages right now)
• Base hash types (e.g. Hash32ByteBase16) should probably live in crypto package

[AngelCastilloB]

Some additional refactoring is needed:

• typedHex() should probably live in util package just like opaqueTypes (seems to be duplicated in core & crypto packages right now)
• Base hash types (e.g. Hash32ByteBase16) should probably live in crypto package

This was addressed in this PR #589

[rhyslbw]

Let's add a notification in the crypto package README, warning users the implementation has not yet been audited, and use at this stage is at own risk. Can also add this in the package.json description.

Feedback addressed