test(smoke): smoke test in rust

[iamquang95]

No description provided.

[iamquang95]

2 CodeQL (go) failed becauses this PR remove all golang code in the repo, so there is no golang code for them to scan

[emlautarom1]

Generally LGTM, I would change the way we're enabling/disabling tests by leveraging different feature flags rather than (ab)using ignored tests.

The flake.nix was still listing go packages (go, gopls and delve). I've pushed an extra comit that removes them and also regenerates the lockfile.

[emlautarom1]

LGTM, but before merging:

pluto/.githooks/pre-push

Lines 29 to 33 in ab044ac

	# Tests
	if ! cargo test --locked --workspace --all-features; then
	echo "❌ Test failures detected"
	exit 1
	fi

The pre-push hook is still using --all-features meaning that smoke tests are included. Drop that or limit it to --features integration (integration tests are actually quite fast).

[emlautarom1]

Also could you add a p2p-udp-address entry next to p2p-tcp-address in the common node flags:

pluto/crates/test-compose/src/lock.rs

Line 145 in ab044ac

Kv::new("p2p-tcp-address", "0.0.0.0:3610"),

Something like Kv::new("p2p-udp-address", "0.0.0.0:3630") should suffice.

#702 wires the quic feature, and since the harness runs nodes with --feature-set=alpha, every node becomes a QUIC-type node once it lands; without a UDP address they install the transport but never listen on it, so the smoke tests never see an actual TCP to QUIC upgrade. With the address set up, all_pluto and mixed_2_charon_2_pluto run the upgrade in both directions. It will show up in the Pluto's logs and as p2p_peer_connection_types{protocol="quic"} on both implementations. The relay already gets 0.0.0.0:3630, so the same port works for nodes. The golden files under testdata/ will need regenerating though.