fix: support macOS VNC connections

[ZacharyZcR]

修复 Support #1206：桌面端 Guacamole WebSocket 不再生成重复 token，并为无用户名的 macOS VNC 密码连接兼容 RFB 003.889 握手。新增远端 URL 与分片握手回归测试，已通过定向测试、ESLint、type-check 和生产构建。

Closes Termix-SSH/Support#1206

[neooriginal]

Shit, you work quickly

Was just about to open my own

[neooriginal]

Thanks for adding the compatibility-proxy path in this PR — it fixes the duplicate desktop token and gets macOS VNC past the private RFB 003.889 banner.

End-to-end testing after merge found one remaining negotiation step: macOS next advertises 30,33,36,2,35, and forwarding that list unchanged lets guacd/libvncclient select Apple/ARD auth type 30. For a username-less connection using the dedicated VNC viewer password, the child then exits instead of choosing classic VNC auth type 2.

I verified a follow-up that filters the Apple security list to type 2 only when type 2 is offered. The real Termix web client then authenticated through guacd 1.6.0 and rendered the macOS lock screen successfully.

• Follow-up PR: fix: force classic auth for macOS VNC #1313
• Tracking issue: [Regression] PR #1311 still selects Apple VNC auth after banner normalization Support#1208
• Earlier report of the type-30 behavior: [BUG] VNC connection to macOS Screen Sharing fails after selecting Apple security type 30 Support#1015