Optimize solverOps array in Verification

[BenSparksCode]

When AtlasVerification.validCalls() is called, it returns a filtered solverOps array.

Instead of leaving blank solverOps objects (checked using solverOp.from == address(0)) in their prev spots in the array, we can pack the array with only the valid ones from the start.

This should see a gas improvement in some cases - in the _execute part of a metacall tx, we can simplify the checks while looping, as well as breaking early after checking only the valid solverOps.

One concern is that rearranging the order of the solverOps array could mess with the simulator. In validCalls, if the call is in simulator mode, the original solverOps array is returned before being filtered. These differences in orders could be problematic.

First pass at mitigating these concerns:

• The isSimulation == true check is now below the solverOps pruning loop, so solverOps returned are in the same pruned form that _execute will receive.
• In the simulator, simUserOperation simulates the metacall with an empty solverOps array (length 0) instead of one of length 1, where it's a single empty solverOp. This change stops the sim call from reverting when it tries to verify the blank solverOp in that pruning loop.

[thogard785]

LGTM!

[jj1980a]

lgtm!