Merge pull request #4873 from driftluo:hole-puching-protocol

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

closes #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.

```mermaid
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
```

Co-Authored-By: driftluo <[email protected]>

Author: doitian

Cargo.lock

@@ -201,7 +201,7 @@ crossbeam = "0.8.2"
 crossbeam-channel = "0.5.1"
 ctrlc = "3.1"
 daggy = "0.8.0"
-dashmap = "4.0"
+dashmap = "6.0"
 derive_more = { version = "1", default-features = false }
 eaglesong = "0.1"
 env_logger = "0.10"
@@ -213,7 +213,11 @@ fs2 = "0.4.3"
 futures = "0.3"
 futures-util = "0.3.21"
 golomb-coded-set = "0.2.0"
-governor = "0.3.1"
+governor = { version = "0.10", default-features = false, features = [
+    "std",
+    "jitter",
+    "quanta",
+] }
 hex = "0.4"
 hickory-resolver = "0.24.2"
 http-body-util = "0.1"

Cargo.toml

@@ -46,11 +46,10 @@ p2p = { workspace = true, default-features = false, features = [
     "ws",
 ] }
 socket2 = "0.5"
+governor.workspace = true
 
 [target.'cfg(target_family = "wasm")'.dependencies]
-p2p = { workspace = true, default-features = false, features = [
-    "wasm-timer",
-] }
+p2p = { workspace = true, default-features = false, features = ["wasm-timer"] }
 idb = "0.6"
 serde-wasm-bindgen = "0.6.5"