[Bug] quic-go版本大于0.46,mihomo版本大于1.18.8容易被反向墙

[ichidog]

Verify steps

• I have read the documentation and understand the meaning of all the configuration items I have written, rather than just piling up seemingly useful options or default values.
• I have carefully reviewed the documentation and have not resolved the issue.
• I have searched the Issue Tracker for the issue I want to raise and did not find it.
• I am a non-Chinese user.
• I have tested with the latest Alpha branch version, and the issue still persists.
• I have provided the server and client configuration files and processes that can reproduce the issue locally, rather than a sanitized complex client configuration file.
• I provided the simplest configuration that can be used to reproduce the errors in my report, rather than relying on remote servers or piling on a lot of unnecessary configurations for reproduction.
• I have provided complete logs, rather than just the parts I think are useful out of confidence in my own intelligence.
• I have directly reproduced the error using the Mihomo command-line program, rather than using other tools or scripts.

Operating System

Linux

System Version

alpine

Mihomo Version

1.19.1

Configuration File

/

Description

我是服务器端用的openwrt23.05.5运行的mihomo搭建了tuicv5和hysteria2两个入站，然后本地使用的lxc的alpine3.21容器运行的mihomo进行tproxy代理，稳定运行了一年，直到一月初更新了1.19.1之后运行两天就发现两个入站节点测速不通，并且本地所有外网都无法访问，只有重启路由重新分配公网ip才恢复正常，后在网上搜索发现是比udp qos更严重的反向墙，之前从来没有遇到过，连udp qos也没有遇到，难道是我本地运营商变得严格了吗，后来我在hysteria2的github issues发现一条疑似 quic-go >= 0.46.0 被部分地区针对 #1220，我就在release查找发现1.18.8是0.46.0之下的,我才想起来我就是从1.18.8更新的1.19.1,后来我把服务端和客户端都回退到了1.18.8，运行了十几天再没有遇到过问题，这种该如何解决,大佬们，不敢更新了😭

Reproduction Steps

自从发现这个问题之后我关注了半个月，发现没有人再提过类似的问题，连那条最早发现的issues至今都无人解决，不过发现最近被udp阻断的人确实变多了，不过大家好像都默认是运营商的问题🤣

Logs