WASM32 - Merge Upstream changes from iotaledger/iota into iota_sdk_abstraction/types

[chrisgitiota]

The folder iota_sdk_abstraction/types contains a subset of the code, used as a wasm32 compatible replacement for the IOTA Client Rust SDK.

The sources in iota_sdk_abstraction/types are currently outdated. The latest state of IOTA Client Rust SDK needs to be cherrypicked and manually merged into iota_sdk_abstraction/types. As only some parts of the Rust SDK code are used in iota_sdk_abstraction/types the code needs to be compared file by file and only changes that apply to code already existing in iota_sdk_abstraction/types shall be merged.

Before doing the upstream merging, we need to consent on a pinned version for the Rust and Typescript IOTA Client SDK.

[wulfraem]

If it helps: a currently known issue, which will be fixed with this PR, is that our interaction types still use the hasPublicTransfer field. This has been removed from the iota crate.

Currently testing locally with these fields commented out in:

• identity_iota_interaction/src/sdk_types/iota_json_rpc_types/iota_object.rs -> IotaParsedMoveObject
• identity_iota_interaction/src/sdk_types/iota_json_rpc_types/iota_object.rs -> IotaRawMoveObject

With the fields commented out, parsing of results from node works again. ^^