Implement SLIP-0023 for Cardano

[supermassive]

Resolves brave/brave-browser#43201
Sec review: https://github.com/brave/reviews/issues/1840

The PR includes:

• Master key generation from bip-39 entropy.
• Private child key generation for normal and hardened indexes.
• Adjusted BoringSSL/OpenSSL methods for pubkey derivation and signing:
  • ED25519_pubkey_from_scalar. Generates pubkey from scalar Ai = [kL]B. Same as part of ED25519_keypair_from_seed but scalar comes from Ed25519_BIP32 algorithm instead of hashed seed
  • ED25519_sign_with_scalar_and_prefix. Same as a part of ED25519_sign. For ED25519_sign private_key[0..31] -> SHA512 -> [scalar, prefix] and private_key[32..63] -> public_key. For ED25519_sign_with_scalar_and_prefix scalar, prefix, public_key come from Ed25519_BIP32 algorithm
  • Also added pseudo random test vectors generated with @cardano-sdk/crypto library

Reference implementations:

• https://github.com/typed-io/rust-ed25519-bip32/blob/master/src/derivation/mod.rs
• https://github.com/input-output-hk/cardano-js-sdk/blob/master/packages/crypto/src/Bip32/Bip32KeyDerivation.ts

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan: