How thought gorilla/websocket altanative plan

### What happened?

Gorilla Web Toolkit was archived in few days ago.
https://github.com/gorilla

Therefore, I thought that we may need to consider migrating to another library or fork gorrila/websocket in the future and created this issue.

### What did you expect?

Currently, it is dependent on a specific Websocket implementation, and we think it would be good if we could mitigate this to some extent.

How about adding new structures or interfaces to allow for more flexible use of Websocket?

### Minimal graphql.schema and models to reproduce

Nothig.

### versions

Nothing.

这个 issue 是关于从已归档的 gorilla/websocket 库迁移出去的。查看 gqlgen 代码库中当前的 WebSocket 实现，可能位于 transport 或 subscription 处理部分。研究适用于 Go 的替代 WebSocket 库，例如 nhooyr/websocket。目标是设计一个接口或结构，对 WebSocket 依赖进行抽象，从而支持未来替换该依赖。查看 issue 中现有的讨论或评论，以了解可能方案的背景。

由索引模型根据 Issue 内容生成。