Add support for libp2p backend in integration tests

[zeegomo]

Ideally, we should test both version in integrations tests, I think it's possible to set up a run for each of the backends right @bacv ?

[bacv]

I think it's possible to set up a run for each of the backends

Yes, integration job builds nomos-node and then runs cargo test with it. With new feature flags, these steps will be duplicated for waku and libp2p.

I can add updated jenkinsfile to this PR or create a new one, which do you prefer?

[bacv]

This probably needs to be in one line for the feature flag.
use nomos_libp2p::{Multiaddr, SwarmConfig};

[danielSanchezQ]

I think it's possible to set up a run for each of the backends

Yes, integration job builds nomos-node and then runs cargo test with it. With new feature flags, these steps will be duplicated for waku and libp2p.

I can add updated jenkinsfile to this PR or create a new one, which do you prefer?

wouldn't the all-features flag work? 🤔

[bacv]

wouldn't the all-features flag work?

It won't work for building two separate binary files. It might work for cargo test, but in order to run integration tests sequentially, every test is executed with a dedicated cargo test command line.

[zeegomo]

wouldn't the all-features flag work?

Backends are mutually exclusive, we actually want duplication here so that we run one time with waku and one time with libp2p.
all-features when building is not possible and in tests would only run each test once (i.e. with only one backend)

[zeegomo]

Right now we use all-features in tests which is causing the test to fail as in the binary/tests waku/libp2p are mutually exclusive features. Can we merge #290 first?