[Bug Report] 机场vless节点connectivity check过不了

### Checks

- [x] I have searched the existing issues
- [x] I have read the documentation
- [ ] Is it your first time sumbitting an issue

### Current Behavior

机场有个vless节点如下：
```
vless://0c8dbf47-xxxx-xxxx-xxxx-xxxxxxxxxxxxx@...:37888?type=tcp&encryption=none&host=&path=&headerType=none&quicSecurity=none&serviceName=&security=reality&flow=xtls-rprx-vision&fp=chrome&sni=nus.edu.sg&pbk=..............&sid=ad6fa889#
```
在手机上的Clash Meta试了这个节点是可用的，但是在dae中的connectivity check过不了：
```
time="Aug 03 14:42:44" level=info msg="Connectivity Check Failed: Head "http://www.gstatic.com/generate_204": nil ecdheKey" network=tcp4 node="HK-..."
...
time="Aug 03 14:42:44" level=info msg="Connectivity Check Failed: Head "http://www.gstatic.com/generate_204": nil ecdheKey" network=tcp6 node="HK-..."
```

### Expected Behavior

这个vless节点在dae中可用

### Steps to Reproduce

错误中提到“nil ecdheKey”，搜代码是在`outbound/transport/tls/reality.go`。

是否是节点tls协议支持的问题呢？

### Environment

- **Dae version (use `dae --version`)**: https://github.com/LostAttractor/dae/tree/dirty
- **OS (e.g `cat /etc/os-release`)**: immortalwrt 24.10.1
- **Kernel (e.g. `uname -a`)**:
- **Others**:

### Anything else?

_No response_

The report points to outbound/transport/tls/reality.go and the “nil ecdheKey” connectivity-check log. Start by reproducing the check with the supplied VLESS Reality node and inspect how that file handles the node’s TLS parameters. Done means determining whether the node is unsupported or the handling is faulty, with a confirmed compatibility result.

Written by the indexing model from the issue text.