feat: enable ledger hardware wallet implementation.

[dawnseeker8]

Description

The PR enable ledger hardware wallet support in Metamask mobiles.

Ledger pre-requisite:

• Patch keyring controller to allow exposing EthKeyringController to support ledger keyring operation
• Adding ledger keyring utils app/core/Ledger/Ledger.ts to support ledger operation, such as add ledger, remove ledger, unlock ledger account, get ledger, connect ledger, open ledger app and close ledger app
• Add Permission-BluetoothPeripheral in IOS pod
• Add self develop ledger keyring library @consensys/ledgerhq-metamask-keyring
• Add ledger offi package @ledgerhq/react-native-hw-transport-ble and react-native-ble-plx

Enable ledger features:

• Pair with Ledger devices via bluetooth, and import ledger accounts into metamask mobile.
• Swap token with ledger account.
• Sending web3 transaction with ledger account. (contract deployment, transfer, authorise etc.)
• Connect Dapp with ledger account and execute rpc operation.
• Sign message with ledger account, supported message type:
  • eth_sign
  • personal_sign
  • eth_signTypedDataV4
• Dispatch sign message event on different stages [REQUEST_SEND, COMPLETE, ERROR] in RPCMethodMiddleware to support ledger sign modal interaction
• Implement required ledger metrics to ledger related screens
• Adding account_type metrics for swap operation and account connect component
• Implementing ExtendedKeyringTypes to consolidate the keyring type from keyring controller and ledger
• Replace fontSize and fontWeight with TextVariant on account label tag related components to adopt theme design

Related issues

Fixes: #1237

Manual testing steps

Need a full regression tests to test all ledger relative feature using https://metamask.github.io/test-dapp/

Screenshots/Recordings

For detailed of screenshot, please refer to our internal Figma design. we will only list out some screenshot below:

Scan devices

Pair with ledger

Transfer

Sign message:

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

5 Bugs
0 Vulnerabilities
0 Security Hotspots
85 Code Smells

12.4% Coverage
0.8% Duplication

[dawnseeker8]

This is the latest smoke e2e tests result https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/74ad83d1-aaea-4065-935b-2d6c220e5d0d

[dawnseeker8]

This is the latest regression e2e tests result: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4553befb-80f7-4c38-883b-7e9a95d6943a

[gantunesr]

I've manually tested the PR and verified the test cases

[Akaryatrh]

I've manually tested the PR and verified the test cases

[georgewrmarshall]

Approving as @brianacnguyen previously mentioned no updates to component-library folder