When store is updated, during the update cycle there's many moments some business code is invoked:

- compute/sort field methods
- onUpdate on fields
- onAdd on fields
- onDelete on fields
- Record.onChange on fields
- any setter on JS record

Lazy fields can also trigger all of the above implicitly.

When mistakes happens in business code and result in crash, usually business code also crashes and this is disruptive enough to continue. However some business code are suspiciously written and want to put crashes into silent. In any cases, the store data insertion is not in a good state.

Before this commit, these crashes prevented the store to flush. In other words, any side-effect of updating store data was never executed after business code crash. This is a problem, because the store is basically non-working, therefore apps that rely heavily on the store show critical bugs, like being unable to mark a Discuss conversation as read.

This commit makes any crash in business code during update cycle resets the flush state of store. Only partial data is inserted in store and some data is lost like before, but at least if some other code tries to insert some other data in store, the store is still able to flush.

opw-4688250