Processor times out when trying to process the full suite of Test262 results

[jcscottiii]

During my experiment with this PR, it turns out that the processor is timing out while trying to process the full test262 suite. And the processor is already at the max timeout out of 60 mins. We need to look at what's causing it (easy: Maybe we can scale the processor up resource wise. more work: see if there's some place in the code we can speed things up or change the architecture so we can have longer timeouts instead of the current flex timeout)

You'll see that task ID 6218904999297024 is just continually retrying on staging.

We need to figure out how to get the processor to ingest everything.

We were bound to hit this problem eventually. But the sheer number of test262 tests made us get here more quickly.