dev: replace transaction hash computation by use of ExecutionV1 type

[greged93]

The below hash computation + signing of the transaction can be replaced by the use of the ExecutionV1 or ExecutionV3 type from starknet-rs. It exposes an API to compute the transaction hash and the signature. The only part that can be a little annoying is that it requires an access to a ConnectedAccount for the signature computation (which doesn't make a lot of sense imo).

Either use a ConnectedAccount with a filled in provider, or keep the current signature derivation and just compute the hash with the type.

ef-tests/crates/ef-testing/src/evm_sequencer/utils.rs

Line 125 in a422e0f

let request = {

[mubarak23]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

I am a Experience Rust / Cairo smart contract developer with experience working on projects such as Just Art Peace, Dojo, Karst, TBA, and Shinigami. Before transitioning to Cairo development, I was a backend developer specializing in Rust.

My recent work with rust

• https://github.com/mubarak23/axum-user-auth
• remove debug info from emitting antoyo/rustc_codegen_gcc#1
• Remove pass test antoyo/rustc_codegen_gcc#5
• feat(balance): add inbound lightning liquidity to GetBalancesResponse fedimint/fedimint#5994
• https://github.com/mubarak23/soroban-bank

How I plan on tackling this issue

• Use ExecutionV1: Instead of manually computing the hash, we now use the ExecutionV1 type from starknet-rs to handle transaction hashing and signing.
• Use ConnectedAccount: The ConnectedAccount object is used to compute the transaction hash and signature through its API.
• Remove manual signing: The old manual signing logic with RELAYER_SIGNING_KEY is removed.