Fix false success and racy counters in generate_eoa_transactions

[damilolaedwards]

Problem

Two problems in the result accounting of generate_eoa_transactions.

• The success, revert and unknown counters were plain ints incremented from per-transaction receipt callbacks, which spamoor runs in their own goroutines. Concurrent increments raced and lost updates.
• The task only waited for those callbacks when awaitReceipt was set. But failOnReject and failOnSuccess derive the result from the same counts, and awaitReceipt is off by default. So with failOnReject: true and the default awaitReceipt: false, the verdict read zeroed counters before the receipts arrived and reported success even when every transaction reverted, silently defeating the requested check.

Fix

• Make the three counters atomic.Int64 so callback increments are not lost.
• Wait for the receipt callbacks whenever the result depends on their counts, that is when awaitReceipt, failOnReject or failOnSuccess is set. The condition is extracted into a helper so it can be tested.

Tests

The wait condition is covered including the failOnReject without awaitReceipt case that previously skipped the wait, and a concurrent increment test confirms the counters do not lose updates and are race free.

go build ./..., go vet, and the package tests under -race pass.