Create an EVM historical event aware actor.

[ryardley]

Currently we have a realtime system which responds to realtime events from the EVM as they are broadcast but we need to be able to collect historical events in an actor from both the eth_getFilterLogs as well as eth_subscribe for future / live events. Which should be committed to disk.

We can change the stream_from_evm function to become an actor that is sent requests to forward to the bus and utilize hydration as referenced within the persistence issue however we will need to store an offset at which events are streamed as part of this actor.