feat(rpc) Implement Filecoin.EthGetLogs

[elmattic]

Summary of changes

Changes introduced in this pull request:

• Partially implement RPC method Filecoin.EthGetLogs

./forest-tool api compare --lotus /ip4/127.0.0.1/tcp/1234/http --forest /ip4/127.0.0.1/tcp/2345/http forest_snapshot_calibnet_2024-10-03_height_2021383.forest.car.zst --filter EthGetLogs -n 800

| RPC Method                | Forest            | Lotus |
|---------------------------|-------------------|-------|
| Filecoin.EthGetLogs (272) | CustomCheckFailed | Valid |
| Filecoin.EthGetLogs (528) | Valid             | Valid |

This PR introduces a new flag/configuration setting (store_events) to retain events in the Tipset cache.

If neither the RPC API nor the methods related to events are used, a value of false can be passed.

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[hanabi1224]

This is much better than Cid tuple!

[LesnyRumcajs]

I'd recommend not using a boolean here - the method has already plenty of parameters and it's cumbersome for the reader what is foo(true, false). A nicer way is above, with an enum - it'd be more readable to have apply_block_messages(..., StoreEvents::Enabled). Additionally, it's more extendible.

What do you think?

[elmattic]

I agree. We can either use another enum. But could we make use of bitflags? (and shave off on param numbers).

[elmattic]

Actually, an enum is the best fit here.

[LesnyRumcajs]

Can we have unit tests for this implementation?

[elmattic]

Can we have unit tests for this implementation?

Sure.

[elmattic]

@ruseinov Not too fast, buster!