Update anytls v0.0.13

[anytls]

Update anytls v0.0.13

• Add disable-reuse option to control session reuse.
• Support data payloads larger than 64KB by splitting them into multiple frames.
• Adjust stream close sequence to ensure proper session cleanup and hook execution.

sing-box:

• Append sing-box/<version> to the client version string to align with other clients.
• Update AnyTLS configuration documentation.

[nekohasekai]

Could you explain why an anti-censorship protocol needs to upload the client name and version? This seems useful only for illicit industries to track users.

[xchacha20-poly1305]

Some airport owners forbidden sing-box via this version info. And the reason is "censors use sing-box as client to detect their server".

[lwb1978]

Could you explain why an anti-censorship protocol needs to upload the client name and version? This seems useful only for illicit industries to track users.

The main issue currently lies in two places within the github.com/anytls/sing-anytls repository:

1. session/session.go references util.Verison;
2. util/version.go defines var Verison = "sing-anytls/0.0.11".
   It is strongly recommended that the anytls project remove the util.Verison variable.

[SakuraFallingMad]

In my view, effective anti-censorship protocols should prioritize appearing indistinguishable from normal network traffic, rather than exhibiting distinctive characteristics that make them easier to identify.

[anytls]

https://github.com/anytls/anytls-go/blob/main/docs/client-name.md

I have documented my design thoughts on the client field in the link above. If this approach is acceptable to sing-box, I can provide a more elegant implementation of the client_metadata configuration option in the next sing-anytls release. However, I against leaving it empty by default.