feat: add a hole punching protocol try use on nat traversal

[driftluo]

What problem does this PR solve?

close #4824 #4766

This PR introduces a protocol to coordinate node connection behavior, attempting to perform TCP traversal through coordination:

1. Removed the try dial observe address behavior.
2. The protocol currently does not support the wasm target and does not support establishing WebSocket protocol connections.
3. The protocol has only three messages, with the following behavior:
   1. Schedule finding peer IDs from the peer store that want to establish a connection and broadcasting their possible listening addresses.
   2. The node receives a Request message and determines if the target object is itself.
      1. If the to object is itself, it returns a Delivered message.
      2. If the to object is not itself, it broadcasts the route and ttl modified.
   3. The node receives a Delivered message response.
      1. If the from object is itself, it starts a TCP connection request and responds with a Sync message
      2. If the from object is not itself, it modifies the route and ttl and propagates the message to the next router object.
   4. The node receives a Sync message response.
      1. If the to object is itself, it starts a TCP connection request.
      2. If the to object is not itself, it propagates the message to the next router object.

sequenceDiagram
    participant A as Initiator Node A
    participant B as Relay Node B
    participant C as Target Node C

    autonumber

    A->>B: ConnectionRequest
    B->>C: Forward(ConnectionRequest)
    activate C
    C-->>C: Validate Target
    C->>B: ConnectionRequestDelivered (incl. Observed Addr)
    deactivate C
    B->>A: Forward(ConnectionRequestDelivered)
    activate A
    A-->>A: Process Reply (Store Observed Addr)
    Note right of A: Delay start early NAT<br/>traversal attempt here (ttl/2)
    A->>B: ConnectionSync
    deactivate A
    B->>C: Forward(ConnectionSync)

    par Start NAT Traversal & Direct Connection Attempt
        activate A
        A-->>A: Start NAT Traversal
        A-->>C: Direct Connection Attempt (e.g., TCP Hole Punching)
        deactivate A
    and
        activate C
        C-->>C: Start NAT Traversal
        C-->>A: Direct Connection Attempt (e.g., TCP Hole Punching)
        deactivate C
    end

Loading

Check List

Tests

• Unit test
• Integration test

Release note

Title Only: Include only the PR title in the release note.

[Copilot]

Copilot reviewed 15 out of 16 changed files in this pull request and generated 1 comment.

Files not reviewed (1)

• util/gen-types/schemas/protocols.mol: Language not supported

[Copilot]

Pull Request Overview

This PR introduces a new TCP hole punching protocol for improved NAT traversal, while removing legacy dialing behavior.

• Adds a “HolePunching” support protocol in config files and network modules.
• Implements protocol components for connection requests, delivered messages, sync messages, and NAT traversal logic.
• Adjusts peer store and network service handling to integrate the new protocol.

Reviewed Changes

Copilot reviewed 15 out of 16 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
util/app-config/src/configs/network.rs	Adds HolePunching enum variant and updates defaults.
resource/ckb.toml	Appends HolePunching to supported protocols list.
network/src/services/outbound_peer.rs	Removes legacy try_dial_observed behavior.
network/src/protocols/support_protocols.rs	Adds protocol string and port for HolePunching.
network/src/protocols/{identify,mod.rs,hole_punching/*}	Implements and integrates new HolePunching protocol.
network/src/peer_store/peer_store_impl.rs	Introduces fetch_nat_addrs and updates observed address logic.
network/src/network.rs	Integrates new HolePunching protocol into network service.

Files not reviewed (1)

• util/gen-types/schemas/protocols.mol: Language not supported

Comments suppressed due to low confidence (2)

network/src/protocols/hole_punching/component/connection_request.rs:186

• The function name 'forword_request' appears to be a typo. Consider renaming it to 'forward_request' to improve clarity.

let content = forword_request(self.message, self_peer_id);

network/src/protocols/hole_punching/component/connection_sync.rs:71

• The function name 'forword_sync' is likely misspelled; renaming it to 'forward_sync' would better reflect its purpose.

let content = forword_sync(self.message);