test!: fix cucumber on libp2p feature branch

[hansieodendaal]

Description

FIx cucumber tests on libp2p feature branch

Notes:

• Instabilities with cucumber when using concurrency other than --concurrency 1 were detected locally, more so for the wallet FFI suite of tests than the normal tests, but --concurrency 1 is recommended for both. This is because addresses are mixed (discoverable) with libp2p when running in the single cucumber process.
• Outstanding issue Fic cucumber access violation (Scenario: As a client I want to be able to restore my ffi wallet from seed words) #6693 to be addressed in a consecutive PR.

Motivation and Context

Some tests were failing

How Has This Been Tested?

• cargo test --release --test cucumber -- --tags "@wallet-ffi and not @broken" --concurrency 1 --retry 2
• cargo test --release --all-features --test cucumber -- --tags "@critical and (not @long-running) and (not @wallet-ffi) and (not @chat-ffi) and (not @broken)" --concurrency 1 --retry 2

What process can a PR reviewer use to test or verify this change?

Code review
Run the cucumber tests

Breaking Changes

• None
• Requires data directory on base node to be deleted
• Requires hard fork
• Other - Please specify

BREAKING CHANGE: Wallet FFI interface change on pub unsafe extern "C" fn comms_config_create

[github-actions]

Test Results (CI)

    3 files    126 suites   9m 26s ⏱️
1 161 tests 1 161 ✅ 0 💤 0 ❌
3 483 runs  3 483 ✅ 0 💤 0 ❌

Results for commit d94ea10.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (Integration tests)

 2 files  10 suites   15m 53s ⏱️
23 tests 22 ✅ 0 💤 1 ❌
25 runs  23 ✅ 0 💤 2 ❌

For more details on these failures, see this check.

Results for commit d94ea10.

♻️ This comment has been updated with latest results.