[Task]: wasm-bindgen-tests or TS tests for iota-interaction-ts functionality

### Feature description

At the moment, functionality provided by `iota-interaction-ts` is only tested implicitly by the products using it.

We need tests in the `iota-interaction-ts` package that test the functionality independently from product specific code.

There are two options to implement these tests:
* [wasm-bindgen-test](https://rustwasm.github.io/wasm-bindgen/wasm-bindgen-test/index.html) driven tests, written in Rust
* Integration tests, written in TS, similar to our already existing product tests

Regarding wasm-bindgen-test it's not clear at the moment if this is a viable solution, as there are many dependencies needed for the tests that might only be available using the IOTA TS Sdk. Additionally, as the recommended way to use wasm-bindgen-test is to [use wasm-pack](https://rustwasm.github.io/wasm-bindgen/wasm-bindgen-test/usage.html#appendix-using-wasm-bindgen-test-without-wasm-pack), it might be hard to integrate our custom build scripts into wasm-bindgen-test.

If tests using wasm-bindgen-test are not realizable, we need to implement tests using TS, based on our usual TS test utilities and test projects (Identity, Notarization, ...).

### Motivation

Test `iota-interaction-ts` functionality independently from product specific code.

### Requirements

-

### Open questions

_No response_

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

No

Start in the iota-interaction-ts package and review the existing product TypeScript test utilities and test projects, including Identity and Notarization. First assess whether wasm-bindgen-test can work with the package dependencies and custom build scripts; otherwise evaluate the TypeScript integration-test approach. Done means iota-interaction-ts functionality is tested independently of product-specific code.

Written by the indexing model from the issue text.