Set consensus timeout conservatively for happy-path integration tests

[youngjoon-lee]

I've found that the first nomos-node sometimes invokes local_timeout, because the consensus timeout was set tightly (10s for 10 nodes), even though it takes 1+ secs for each nomos-node to be started:

nomos-node/nomos-services/consensus/src/network/adapters/libp2p.rs

Line 237 in d479721

tokio::time::sleep(std::time::Duration::from_secs(1)).await;

For happy tests, we need to see the consensus timeout conservatively, so that timeout doesn't happen at the startup phase.

This will solve the following CI failure in the master branch and #445 (comment).

timed out waiting for nodes to reach view 20

Please note that I haven't changed the test timeout 20s:

nomos-node/tests/src/tests/happy.rs

Line 18 in 7fcfe89

let timeout = std::time::Duration::from_secs(20);