Add espresso dev node to cartesi run

[endersonmaia]

📚 Context

So that developer can experiment applications using espresso sequencer during local development, we need to provide a espresso dev node as a service.

✔️ Solution

Add the espresso dev container to our compose

https://github.com/EspressoSystems/espresso-sequencer/blob/main/doc/espresso-dev-node.md

📈 Subtasks

• add espresso dev node as a container to our compose
• publish its API through traekif ever proxy
• explicitly enable the service with --enable-espresso

🎯 Definition of Done

• cartesi run should start an espresso dev node and export its API endpoint to localhost

[endersonmaia]

Whe I start a espresso-dev-node connected to anvil and postgres from cartesi run I can see that the sequencer database created for espresso gets populated and I see at anvil logs that some contracts are created.

We can see in dev-info API we have the LIghtClient address, for ex.:

curl -fsSL -X GET localhost:20000/api/dev-info | jq .
{
  "builder_url": "http://localhost:8771/",
  "l1_prover_port": 8772,
  "l1_url": "http://anvil:8545/",
  "l1_light_client_address": "0x5f3f1dbd7b74c6b46e8c44f98792a1daf8d69154",
  "alt_chains": []
}

[endersonmaia]

At the logs, I get some errors that I can't understand yet.

This appears two times at the beginning:

  2024-09-30T13:25:58.118222Z ERROR sequencer::context: Cannot get info from orchestrator client
    at sequencer/src/context.rs:282

  2024-09-30T13:25:58.118240Z ERROR hotshot: HotShot is running with the dependency tasks feature enabled!!
    at /home/runner/.cargo/git/checkouts/HotShot-de3b585b288dcaaa/8b68188/crates/hotshot/src/lib.rs:354

This loops forever:

 2024-09-30T13:25:45.771230Z ERROR hotshot_task_impls::transactions: Timeout while getting available blocks, err: future has timed out
    at /home/runner/.cargo/git/checkouts/HotShot-de3b585b288dcaaa/8b68188/crates/task-impls/src/transactions.rs:585
    in hotshot_task_impls::transactions::wait_for_block with id: 0, cur_view: 477, block_view: 478
    in TransactionTaskState::Transaction task with id: 0, view: 477
    in TransactionTaskState::Transaction task with id: 0, view: 476

I eventually saw this too:

Loading SRS from Aztec's ceremony...
Done in 66.260ms
Generating proving key and verification key.
Done in 4.400s