feat: use decryptAsync/encryptAsync for remaining WRW flows

[bdesoky]

Ticket: WCN-172

This pull request refactors key recovery and encryption/decryption logic across multiple coin modules and the BitGo SDK to consistently use asynchronous methods, improving reliability and compatibility with async workflows. The main changes involve replacing synchronous key derivation and encryption/decryption functions with their asynchronous counterparts, and updating method signatures and calls accordingly.

Key changes include:

Asynchronous Encryption/Decryption

• Replaced all calls to synchronous decrypt and encrypt methods with their asynchronous equivalents (decryptAsync and encryptAsync) throughout the SDK, including wallet recovery, transaction signing, and key sharing operations in wallet.ts and ecdsaMPCv2.ts. This ensures that encryption and decryption operations do not block the event loop and are compatible with async/await patterns. [1] [2] [3] [4] [5] [6] [7] [8] [9]

Asynchronous Key Derivation

• Updated all usages of getBip32Keys to use the asynchronous getBip32KeysAsync function in UTXO, EOS, STX, TRX, and XRP coin modules, as well as related imports, to ensure proper handling of asynchronous key derivation. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

ECDSA MPCv2 Recovery Key Changes

• Modified all calls to ECDSAUtils.getMpcV2RecoveryKeyShares to include the bitgo instance as an additional argument, ensuring that recovery key shares are generated with the correct context and access to required BitGo methods. [1] [2] [3] [4] [5] [6] [7] [8]

These updates standardize async key management and cryptographic operations across the codebase, reducing the risk of blocking behavior and improving maintainability.

[linear-code]

WCN-172

[vinhkhangtieu]

use async for decrypt and encrypt

[pranavjain97]

lgtm