Wallycore

- No API changes

- No API changes

- API change of wally_tx_to_bytes and wally_tx_to_hex to not accept
WALLY_TX_FLAG_USE_ELEMENTS set in flags. You should remove this flag when
upgrading. This change affects elements transactions only.

- Invalid bech32 addresses may have caused an out of bounds read. Thanks to
Christian Reitter and Dr. Jochen Hoenicke for finding and reporting this
issue. All users are advised to upgrade as soon as possible to minimise
any potential impact.

- BIP38_KEY_TESTNET was changed to reflect the testnet network version. BIP38 testnet keys
created with older versions of wally were not valid for testnet.

- API change of wally_tx_elements_input_init_alloc and wally_tx_add_elements_raw_input
to also include the pegin witness.

- WALLY_SECP_RANDOMISE_LEN was renamed to WALLY_SECP_RANDOMIZE_LEN for
consistency - You should change any references in your source when upgrading.

- A potential crash when parsing short base58check strings was fixed. Users
are encouraged to upgrade to 0.6.4 if they parse untrusted/unvalidated
base58check input into short (less than 5 byte) output buffers.

- No API changes