node: pin the max-peers inbound-reject log to the handshake tracing target

The debug log for rejecting an over-cap inbound connection is emitted from
the peer-action executor, under that module's tracing target. Nodes that
raise only the handshake module to debug (leaving other modules at info) no
longer surfaced the rejection, so cap-enforcement events were invisible in
their logs. Re-pin the log to the handshake target, matching the adjacent
promoting-inbound log, so the rejection stays visible under a
handshake=debug filter regardless of the executor module's own level.

src/node/dataplane/peer_actions.rs

@@ -276,6 +276,12 @@ impl Node {
                             // failures remain at warn.
                             if matches!(e, NodeError::MaxPeersExceeded { .. }) {
                                 debug!(
+                                    // Emit under the handshake target (same as the
+                                    // "promoting inbound" line above) so this stays
+                                    // visible wherever inbound handshake events are
+                                    // logged at debug, independent of this module's
+                                    // own log level.
+                                    target: "fips::node::handlers::handshake",
                                     peer = %self.peer_display_name(ambient.verified_identity.node_addr()),
                                     max = self.max_peers(),
                                     "Rejecting inbound connection at max_peers cap (no promotion)"