feat: custom derivation paths in Mnemonic ECDSA private key derivation

bguiz commented 5 months ago

Description:

What

Compatibility/ parity with EVM dev tools + wallets. Specifically:
- When working Metamask, you need to use the hardcoded derivation path in it, and in SDK there's also a (different) hardcoded derivation path.
- In EVM dev tools - web3.js/ethers.js/viem etc - they allow you to specify a custom derivation path, and do not force you to use the Ethereum one.
The lack of support for custom derivation paths is a friction point for EVM developers onboarding into Hedera development
- This may have the effect of effectively discouraging use of the SDK, in favour of using 3rd party libraries that do support custom derivation paths
we should aim to reduce the reliance on 3rd party dependencies in general, within code that is written using the SDK
- The following examples demonstrate that (1) additional code is needed, and (2) additional 3rd party dependencies need to be brought in:
- example of extra code required in JS: https://github.com/hedera-dev/scratch-hello-world/blob/60fa4007/js-hello-world/00-create-fund-account/script-create-fund-account.js#L19-L23
- example of extra code required in Java: https://github.com/hedera-dev/scratch-hello-world/blob/60fa4007/java-hello-world/00-create-fund-account/src/main/java/createfundaccount/ScriptCreateFundAccount.java#L30-L55
- example of extra code required in Go: https://github.com/hedera-dev/scratch-hello-world/blob/60fa4007/golang-hello-world/00-create-fund-account/script-create-fund-account.go#L37-L61