Correct LANGUAGES.md entries flagged after the matrix update

[slachiewicz]

Follow-up to #3820, addressing the two review comments there. Every entry was checked against the source at 5c5e93e; nothing here is carried over from the earlier matrix.

Entry	Was	Now	Evidence
Java SE levels	11 / 19	8 / 17	build.yml builds on JDK 17 and runs the cross-tests on Java 8; sourceConfiguration.gradle sets a JDK 17 toolchain with options.release = 8
Rust TLS	no	yes	the rustls feature in Cargo.toml, with TTlsClientChannel::connect and TServer::listen_tls
Rust Domain	no	yes	TServer::listen_uds, under #[cfg(unix)]
Rust ThreadPool	no	yes	TServer holds a ThreadPool sized by num_workers
Python Memory, Framed	no	yes	TMemoryBuffer and TFramedTransport
Python Threaded, ThreadPool	no	yes	TThreadedServer and TThreadPoolServer
Kotlin level	1.8	2.4.10	settings.gradle.kts uses kotlin("jvm") version "2.4.10"; 1.8 is the bytecode target, not the Kotlin version
Kotlin Multiplex, zlib, Nonblocking, ThreadPool	no	yes	the cross-test server uses TMultiplexedProcessor, TZlibTransport, TNonblockingServer and TThreadPoolServer over the Java runtime
Haxe Memory	no	yes	TMemoryStream, with round-trip coverage in StreamTest.hx

The table has no way to carry a condition, so this adds a short notes section for three of them: the rustls feature is off by default, listen_uds is Unix-only, and the Java and Kotlin rows report tested bounds rather than a maximum supported release.

One entry is deliberately left alone. Rust has a single server type, a fixed-size worker pool, and the row marks it as both Threaded and ThreadPool. Marking ThreadPool is right; whether Threaded should stay is a separate judgement, and I did not want to fold it into a corrections PR.

Thanks @HTHou for the two lists. The claims held up on inspection.

This change was created with AI assistance.

[slachiewicz]

While table looks nice maybe it coudl be somehow reorganized to some capabilities and more verbose clarification that this capability means for specific language. For example Go port is in many places marked as "not supported" due to different architecture.
But i'm too new to make decisions here, simpy found that we have outdated page with features while reviewing AI tool output.

[HTHou]

Thanks for following up! The changes address all the entries raised in the two comments on #3820, and the added notes clarify the platform, feature and version conditions.

Reviewed the documentation changes against the source and build configuration with AI assistance; I did not rerun the test suite locally. No blocking issues found in this diff. The Rust Threaded/ThreadPool terminology can be discussed separately.