e2e tests failing with ink-node `v0.43.3`

[AlexD10S]

When using a chain with the latest version of pallet_revive, such as ink-node v0.43.3 https://github.com/use-ink/ink-node/releases/tag/v0.43.3 e2e tests are failing.

The e2e crate needs to be updated to reflect the latest changes in pallet_revive tracing. Relevant upstream changes include:

• https://github.com/paritytech/polkadot-sdk/pull/7166
• https://github.com/paritytech/polkadot-sdk/pull/7167
• Example of the changes in a chain: https://github.com/paseo-network/passet-hub/pull/15

Error output:

error on ws request `trace_tx`: User(UserError { code: 4003, message: "Client error: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed\nWASM backtrace:\nerror while executing at wasm backtrace:\n    0: 0x20b938 - ink_node_runtime.wasm!rust_begin_unwind\n    1: 0xed65 - ink_node_runtime.wasm!core::panicking::panic_fmt::hfdb65cc345fb23df\n    2: 0xd8f78 - ink_node_runtime.wasm!ReviveApi_trace_tx", data: None })

User error: Client error: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
WASM backtrace:
error while executing at wasm backtrace:
    0: 0x20b938 - ink_node_runtime.wasm!rust_begin_unwind
    1: 0xed65 - ink_node_runtime.wasm!core::panicking::panic_fmt::hfdb65cc345fb23df
    2: 0xd8f78 - ink_node_runtime.wasm!ReviveApi_trace_tx (4003)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

How to Reproduce

To see the issue on master with ink-node v0.43.3:

export CONTRACTS_NODE="path-to-ink-node/ink-node-v0.43.3"
git checkout master
cargo contract test --all-features --manifest-path integration-tests/public/flipper/Cargo.toml --nocapture

Reported by @davidsemakula on Element