Add retry logic to the `BatchedExpressionEvaluator`

[elliette]

Currently, if any of the expressions in the BatchedExpressionEvaluator fail, then all the expressions fail.

When this happens, we should re-try the expressions individually.

[annagrin]

Retrying individually is too expensive unfortunately - the flutter widget inspector won't be responsive in this case (will take ~15 sec to show node's children on hover), and most likely all of them will fail if one does, as the failures we are currently seeing are a not an expected behavior and is probably due to a bug in how and why the evaluate() is called, or a missing evaluate() case support in dwds, or both:)

Normal failures (such as compilation errors) should be handled already.

[bkonyi]

It sounds like expression evaluation is failing due to implementation issues within DWDS, not necessarily due to bad expressions. Maybe we should consider prioritizing fixes for these DWDS issues rather than implementing retry logic.