Feat : Trace_transaction RPC call implementation

[Tbelleng]

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

• Feature ✅

What is the new behavior?

Add trace_transaction RPC call and modify trace_block_transactions ✅
In this new implementation, we are going to separate transactions from a block into 2 vectors,
the first one contains transactions that we dont want to trace but we still need to re-execute them in order to
get the correct state update.

The second vector contains transactions that we want to re-execute and trace.

⚠️ So for trace_block_transactions method, we are gonna re-execute and trace all transactions within a block, but concerning trace_transactions method, we will only target and put the transactions needed into the second vector to get its trace.

Does this introduce a breaking change?

No ❌

Other information