bench: consider receipt status for successful tx reporting

[mooori]

Regarding the metric near_transaction_processed_successfully_total:

One important thing to keep in mind is that this metric is incremented when the transaction successfully converts into a receipt. It does not mean that the receipt is actually getting executed (it might even happen in a different block if the receipt gets delayed.) You will probably want a metric along the lines of near_action_called_count (allows determining the rate of actions based on action types even in mixed action workloads, or where receipts have multiple actions!) or receipts (I don't think we have a single metric for all of them together, but shouldn't be too hard to add up the delayed, local, incoming, etc. receipts.)

Originally posted by @nagisa in #12874 (comment)

Affected tooling:

• benchmarks/synth-bm
• tx pool injection native transactions benchmark bypassing the json-rpc layer #12899
• FT Locust workload (and perhaps other Locust workloads too)