Add clash count to benchmarks

[FrancoGiachetta]

This PR adds the class hash call to the logs for each transaction, with its entrypoint, during block range's benchmark execution.

{"timestamp":"2024-09-05T13:37:52.754794Z","level":"INFO","fields":{"message":"finished tx execution","time":"13.950873625s"},"target":"replay::benchmark","span":{"class_hash_called":"0x3131fa018d520a037686ce3efddeab8f28895662f019ca3ca18a626650f7d1e","entry_point_used":"0x15d40a3d6ca2ac30f4031e42be28da9b056fef9bb7357ac5e85627ee876e5ad","transaction_hash":"139602690545065343768301486723194920031895487956458237324480318165151840881","name":"tx execution"},"spans":[{"name":"caching block range"},{"block_number":633333,"name":"block execution"},{"class_hash_called":"0x3131fa018d520a037686ce3efddeab8f28895662f019ca3ca18a626650f7d1e","entry_point_used":"0x15d40a3d6ca2ac30f4031e42be28da9b056fef9bb7357ac5e85627ee876e5ad","transaction_hash":"139602690545065343768301486723194920031895487956458237324480318165151840881","name":"tx execution"}]}

[github-actions]

✅ Code is now correctly formatted.

[JulianGCalderon]

Right now, the class_hash and entry_point information are only associated to the execution summary and, if we ever want to analyze and plot this information) there is no easy way to link them to the execution time (they are in different events on the same span).

I think it's better if, instead, you record that information into the span (_tx_span). If there is a way to get the class hash and the entry point before the execution, you can add it directly, if this is not possible, you can use this method: https://docs.rs/tracing/latest/tracing/struct.Span.html#method.record to record it afterwards.

Ask me If you have any questions about this.

[FrancoGiachetta]

Might be a way to gather the entrypoint through the transaction's calldata. But I think it´s more redable to leave as it is now and use that record method you were talking about.

[JulianGCalderon]

@FrancoGiachetta can you resolve the conflicts on this branch?