test: add target_connections logging to debug flaky connect tests

Add detailed logging to the Connect operation's handle_response method
to capture:
- target_connections value at response receipt
- accepted_count before and after register_acceptance
- satisfied result

This will help diagnose why test_gateway_reconnection occasionally times
out despite receiving ConnectResponse - we need to verify whether
target_connections is being set correctly to 1 for 2-node test networks.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: sanity

crates/core/src/operations/connect.rs

@@ -671,12 +671,21 @@ impl ConnectOp {
                 tracing::info!(
                     acceptor_pub_key = %response.acceptor.pub_key(),
                     acceptor_loc = ?response.acceptor.location(),
+                    target_connections = state.target_connections,
+                    accepted_count = state.accepted.len(),
                     "connect: joiner received ConnectResponse"
                 );
                 let result = state.register_acceptance(response, now);
                 if let Some(new_acceptor) = &result.new_acceptor {
                     self.recency.remove(&new_acceptor.peer);
                 }
+                tracing::info!(
+                    tx = %self.id,
+                    satisfied = result.satisfied,
+                    accepted_count = state.accepted.len(),
+                    target_connections = state.target_connections,
+                    "connect: register_acceptance result"
+                );
                 if result.satisfied {
                     tracing::info!(
                         tx = %self.id,