Overriding target round into future causes algod importer to appear stalled.

### Subject of the issue

If you override the target round to some point in the distant future, the algod importer will appear to stall at the init stage waiting for that round to be reached.

In some cases, it could be desired to have Conduit wait for a point in the near future, but it does not seem useful to have it wait for an unbounded amount of time. Especially not without any output.

### Steps to reproduce

1. With a no-op exporter, start conduit with a large round override like `-r 999000000`.
2. Conduit log stalls at:
* If a catchpoint was used: `Catchpoint catchup finished in ...`
* If a catchpoint was not used: `Pipeline round: 999000000` message.
3. Observe that algod is caught up with `goal node status`

### Expected behaviour

Periodic log messages about the current node round and the target round.

### Actual behaviour

No output