chore(cache): move cache system out of config

[Evalir]

There's no reason for this to be contained here, and feels wrong when every other task has its own file / spawn pattern.

[Evalir]

• chore(cache): move cache system out of config #118 👈 (View in Graphite)
• chore(repo): update rust to latest #117
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[prestwich]

this API doesn't match our idiom. our idiom is to

• instantiate a struct let my_struct = MyStruct::new(...)
• call my_struct.spawn()

CacheSystem is not a spawnable task in this way, it;s only a holder for the join handles and a ref to the simcache to ensure it is not prematurely dropped

if you want to make a spawnable CacheTasks then it should be a composition of the 2 component tasks that spawns both of them

struct CacheTask {
    /// The transaction poller task.
    pub tx: TxPoller,

    /// The bundle poller task.
    pub bundle: BundlePoller
}

[prestwich]

NACK on the new api. suggested an improvement that's in our idiom.

[Evalir]

Note that this is not a new api—this was just moved from the config file. I'll update to the newly proposed API

[prestwich]

it's not new logic, it is a new API