[Request]: Update to latest IOTA version and upstream merge sdk_types

### Feature description

> [!NOTE]
> THIS IS A PERMANENT ISSUE AND WILL USUALLY NOT BE CLOSED
>
> This issue can only be closed when all TF components are published to crates.io

To leverage compatibility with the latest IOTA version we need to release most TF products in a bi weekly schedule using the latest IOTA mainnet version as dependency.

This needs to be done until all TF components are are published to crates.io.

Tasks after IOTA `testnet` release (release candidate):

- Create test branches in the `product-core`, `identity` and `notarization` GH repositories to prepare new product versions and to test these products using the IOTA release candidate
- In `product-core`: Make sure that the IOTA Interaction SDK types implementation (needed to provide npmjs packages) is kept in sync with the latest IOTA version
- In `product-core`: Check if the following dependencies have changed: `tokio`, `fastcrypto`
- In `product-core`: Check if there is a new npmjs version for `@iota/iota-sdk` and, in case it is, set a new peerDep. version for `@iota/iota-sdk` in `bindings/wasm/iota_interaction_ts`

Tasks after IOTA `mainnet` release (release candidate):
- Release a new product-core version and `@iota/iota interaction-ts` npmjs package
- Test Identity and Notarization using the new `product-core` version
- Prepare the bi weekly release of `identity` and `notarization`

### Motivation

Foster compatibility with the latest IOTA version

### Requirements

TODO

### Open questions

_No response_

### Are you planning to do it yourself in a pull request?

Yes