Add support for bip39 with other wordlists

[jacogr]

We are pulling in the extra wordlists via #1803

This has been PR-ed previously in #1689 and there has been some discussion. However after giving it some thought, we could actually make this work.

part 1

1. We need a wordlist option passed to the bip39 functions, e.g. last param of wordlist: string[] = DEFAULT_WORDLIST -

common/packages/util-crypto/src/mnemonic/bip39.ts

Line 53 in 91a2eac

export function mnemonicToEntropy (mnemonic: string): Uint8Array {

common/packages/util-crypto/src/mnemonic/bip39.ts

Line 95 in 91a2eac

export function entropyToMnemonic (entropy: Uint8Array): string {

2. We change the DEAFULT_WORDLIST usage in these functions so be wordlist instead.
3. Add actual tests for these in bip39.spec.ts to ensure we are actually ok.

part 2

Now the base generation is ok, but we may still use the wasm versions which doesn't have support for this. To get around it -

1. Adapt the wasm/js check inside the exposed functions to also take in a last param of wordlist?: string[], onlyJs?: boolean

common/packages/util-crypto/src/mnemonic/validate.ts

Lines 22 to 23 in 91a2eac

	export function mnemonicValidate (mnemonic: string, onlyJs?: boolean): boolean {
	return !hasBigInt || (!onlyJs && isReady())

common/packages/util-crypto/src/mnemonic/toMiniSecret.ts

Line 11 in 91a2eac

export function mnemonicToMiniSecret (mnemonic: string, password = '', onlyJs?: boolean): Uint8Array {

common/packages/util-crypto/src/mnemonic/toLegacySeed.ts

Line 27 in 91a2eac

export function mnemonicToLegacySeed (mnemonic: string, password = '', onlyJs?: boolean, byteLength: 32 | 64 = 32): Uint8Array {

common/packages/util-crypto/src/mnemonic/toEntropy.ts

Line 9 in 91a2eac

export function mnemonicToEntropy (mnemonic: string, onlyJs?: boolean): Uint8Array {

common/packages/util-crypto/src/mnemonic/generate.ts

Line 21 in 91a2eac

export function mnemonicGenerate (numWords: 12 | 15 | 18 | 21 | 24 = 12, onlyJs?: boolean): string {

2. For these treat the wordlist the same as onlyJs, i.e. when passed in we want to take the JS (non-WASM) route, i.e. it ties into the changes we made in bip39.ts. This looks something like !hasBigInt || (!wordlist && !onlyJs && isReady()) and the param passed on the JS-only path
3. For all the above add tests...

part 3

Now we also need keyring support -

1. Make the required wordlist-in changes to addFromMnemonic, addFromUri & createFromUri in

   common/packages/keyring/src/keyring.ts

   Lines 201 to 223 in 8920045

   	/**
   	* @name createFromUri
   	* @summary Creates a Keypair from an suri
   	* @description This creates a pair from the suri, but does not add it to the keyring
   	*/
   	public createFromUri (_suri: string, meta: KeyringPair$Meta = {}, type: KeypairType = this.type): KeyringPair {
   	// here we only aut-add the dev phrase if we have a hard-derived path
   	const suri = _suri.startsWith('//')
   	? `${DEV_PHRASE}${_suri}`
   	: _suri;
   	const { derivePath, password, path, phrase } = keyExtractSuri(suri);
   	let seed: Uint8Array;
   	const isPhraseHex = isHex(phrase, 256);
   	if (isPhraseHex) {
   	seed = hexToU8a(phrase);
   	} else {
   	const parts = phrase.split(' ');
   	if ([12, 15, 18, 21, 24].includes(parts.length)) {
   	seed = type === 'ethereum'
   	? mnemonicToLegacySeed(phrase, '', false, 64)
   	: mnemonicToMiniSecret(phrase, password);

2. Add tests...

[jacogr]

#1805 adds support for the first part above.
#1814 adds support for the second part above.