Curio Devnet fails silently

# Summary

The current Curio Devnet setup fails silently. It is not reporting any errors, so CI is green, but Curio is not running correctly. Lotus Miner does all the work.

[Sample passing CI.](https://github.com/ChainSafe/forest/actions/runs/12890066623/job/35939284699)

@lemmih did some testing, outcomes:

1. In CI, Curio is repeatedly failing and restarting.
2. Locally, it fails with Yugabyte errors, e.g., `No db connection string found`. This is not present in CI for some reason (but it still fails).
3. The failures started before the [version bump](https://github.com/ChainSafe/forest/pull/5156). This might mean we had a regression that was missed.

This means that we have no way of ensuring that Forest works with Curio in the current state.

# Completion Criteria

- [ ] Identify and fix the issue with Curio + Forest on devnet
- [ ] Ensure CI check is red when Curio + Forest fails in any way to catch future regressions and assert fix is correct. This might mean additional assertions will be needed. Curio **must** mine some blocks after epoch 10.

# Additional Links & Resources