ECSStateStoreCommitterThroughputST intermittent failure

### Description / Background

On 30/06/2026 the test ECSStateStoreCommitterThroughputST shouldMeetExpectedThroughputWhenCommittingFilesWithNoJobOnOneTable failed on the expectedCommitsPerSecondForTransactionLogOnly check as:
Expecting actual:
25.161663689203127
to be greater than:
100.0

We haven't see this failure again but the logs are available in the nightly system tests s3 bucket.

This test needs looking into to see what could have caused this.

Avenues to investigate:
Did the test experience a cold start which caused this?
Is there a problem with the implementation of this test in comparison to the other ECSStateStoreCommitterThroughput tests?
Is there an issue with how the logs are processed?

Start with ECSStateStoreCommitterThroughputST, especially shouldMeetExpectedThroughputWhenCommittingFilesWithNoJobOnOneTable, and compare it with the other ECSStateStoreCommitterThroughput tests. Inspect the available logs in the nightly system tests S3 bucket and trace the expectedCommitsPerSecondForTransactionLogOnly check. Done means identifying whether the failure came from a cold start, test implementation, or log processing and recording or addressing the cause.

Written by the indexing model from the issue text.