call-block-logs makes worker run out of heap memory

[TimDaub]

• the updated get-block-logs strategy just shoves lot of messages into the queue and then the process crashes: https://github.com/neume-network/strategies/blob/4c929075d8323d7449db7fa7b376d30aaf3dee4e/src/strategies/call-block-logs/extractor.mjs#L47
• While, sure, the user should not carelessly spam messages to the worker: I think the worker should provide the greatest possible freedom to the strategy implementor. So we should investigate if we can prevent the worker from running out of memory by e.g. storing state on the fs (which the better-queue may support)

  neume-network-strategies:lifecycle Starting extractor strategy with name "call-block-logs" with params "[11565020,15283124]" +0ms
2022-08-06T19:27:44.072Z neume-network-extraction-worker:worker Starting as worker thread with queue options: "{"concurrent":2}
events.js:377
      throw er; // Unhandled 'error' event
      ^

Error [ERR_WORKER_OUT_OF_MEMORY]: Worker terminated due to reaching memory limit: JS heap out of memory
    at new NodeError (internal/errors.js:322:7)
    at Worker.[kOnExit] (internal/worker.js:276:26)
    at Worker.<computed>.onexit (internal/worker.js:203:20)
Emitted 'error' event on Worker instance at:
    at Worker.[kOnExit] (internal/worker.js:276:12)
    at Worker.<computed>.onexit (internal/worker.js:203:20) {
  code: 'ERR_WORKER_OUT_OF_MEMORY'
}

crawl_path

[{ name: "call-block-logs", extractor: {args: [11565020, 15283124]}}],