Language bindings, KDE thumbnails, yapf compare, in-memory encoding

- yapf_encode() / yapf_free_buffer(): encode to memory; yapf_save uses it
- yapf.c also compiles as C++
- `yapf compare`: size and decode speed of the original format vs YAPF,
  with a lossless check
- bindings with tested examples: C++ (header-only), C# (P/Invoke),
  Rust (crate, builds the C code), Go (cgo), Java (FFM API, Java 22+),
  Zig (@cImport), LuaJIT (FFI), TypeScript types for the JS port;
  Python now encodes in memory
- docs/LANGUAGES.md and examples/ with measured results
- KDE Dolphin thumbnail plugin (KF6, CMake)
- README: honest status for Photoshop / VS Code / Figma (not run in the
  apps yet) and macOS (cross-compiled only), platform table

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

bindings/java/README.md

@@ -0,0 +1,16 @@
+# YAPF for Java (and Kotlin)
+
+`Yapf.java` uses the Foreign Function & Memory API of **Java 22+** — no JNI,
+no native glue to build; just the YAPF shared library (`yapf.dll`,
+`libyapf.so`, `libyapf.dylib`) on the library path or passed with
+`-Dyapf.library=/path/to/lib`.
+
+```java
+Yapf.Image img = Yapf.load(Path.of("texture.yapf"));    // or Yapf.decode(bytes)
+byte[] file = Yapf.encode(new Yapf.Image(256, 256, 4, rgba));
+```
+
+Kotlin can call the same class directly.  Run with
+`--enable-native-access=ALL-UNNAMED` to silence the native-access warning.
+
+Example: `java --enable-native-access=ALL-UNNAMED -Dyapf.library=../../build/libyapf.so Example.java`