FEVM: Re-execute tipset on missing events

[Stebalien]

If an Eth JSON-RPC API like EthGetTransactionReceipt fails because we're missing the transaction's events (e.g., because we enabled the Ethereum API after we processed the tipset, we should re-execute the tipset.

This will cause some work on otherwise pure "lookup" API requests however, this should only happen once and it should only happen for "old" tipsets. Although we do need to make sure that it only happens once (we may need some way to lock/deduplicate such requests?).

See #11325.

[Stebalien]

Alternatively:

1. Re-compute events in

   lotus/node/impl/full/chain.go

   Line 706 in 9fc3c33

   func (a *ChainAPI) ChainGetEvents(ctx context.Context, root cid.Cid) ([]types.Event, error) {

   on-demand.
2. Fix the TODO so we actually use this everywhere.

That's probably better?

[Stebalien]

The biggest hurdle here will be deduplicating the work. That is, StateManager.TipSetState coalesces all requests to compute a single tipset into a single request. However, it also avoids re-doing the computation if the state for that tipset (and the receipts) exist, without checking if the events associated with those receipts exist.

So fixing this will actually be a bit tricky. We could make the TipSetState function re-compute tipsets if we don't have all events, but that would force us to load the receipts/events to check (which isn't free).