docs: standardise language naming + binding security sections (#290)

* docs: standardise language naming and add binding security sections

Canonical binding list everywhere: Rust, Python, Node.js, WASM, C, C++, C#,
Go, Java, R. Use C# (not .NET) as the language label, WASM (not WebAssembly)
in prose, and frame the C ABI as a hub rather than a list item.

- Bump stale indicator counts (200+ -> 514) and family count (sixteen ->
  twenty-four) in the Node/Python/WASM and docs READMEs.
- Add a short Security section to all eight binding READMEs.
- Relabel benchmark rows (C -> C / C++, C# / .NET -> C#).
- Fix the 'language stecker' wording in the C#/Go/R API intros.
- Documentation only; no code or public API changes.

* release.yml: extend install snippets and expose version output

Add the missing registry installs to the release body (dotnet, go, Gradle/
Maven Central, r-universe) alongside cargo/pip/npm, and expose a v-stripped
'version' output from the tag step for the Gradle coordinate. Also fix the
C-ABI language order in the assets note (C# before Go).

* release.yml: correct the release body (10 languages, all registries)

Reframe the tagline to '10 languages' (native Rust/Python/Node.js/WASM + a C
ABI hub for C, C++, C#, Go, Java, R) instead of '4 language registries', note
that C#/Java/Go/R publish to NuGet/Maven/Go/r-universe via their own jobs, and
tidy the Node.js label and the C-ABI hub list.

BENCHMARKS.md

@@ -98,8 +98,8 @@ python -m benchmarks.compare_libraries
 ## 3. Per-binding throughput — the cost of the boundary
 
 The sections above compare Wickra against other libraries, which only exists for
-Python and Rust (there is no comparable streaming TA library for C, C#, Go, Java,
-R or WebAssembly to benchmark against). Every binding calls the **same** Rust
+Python and Rust (there is no comparable streaming TA library for C, C++, C#, Go, Java,
+R or WASM to benchmark against). Every binding calls the **same** Rust
 core, so these per-binding benchmarks are **not** a speed claim and **not** a
 cross-library ratio — they document the raw cost of crossing each language's FFI
 boundary, in million updates per second (Mupd/s).
@@ -127,12 +127,12 @@ AMD Ryzen 9 9950X):
 | Target               | streaming (Mupd/s) | batch (Mupd/s) |
 |----------------------|-------------------:|---------------:|
 | Rust core (no FFI)   |                391 |            500 |
-| C                    |                383 |            330 |
-| C# / .NET            |                337 |            244 |
+| C / C++              |                383 |            330 |
+| C#                   |                337 |            244 |
 | Python               |                 33 |            488 |
 | Java                 |                 28 |            175 |
 | Go                   |                 24 |            400 |
-| WebAssembly          |                 19 |            167 |
+| WASM                 |                 19 |            167 |
 | Node.js              |                 17 |             10 |
 | R                    |                0.1 |            193 |
 
@@ -160,7 +160,7 @@ node bindings/node/benchmarks/throughput.js                       # native napi-
 cargo build -p wickra-c --release                                 # the C ABI hub
 cmake -S bindings/c/benchmarks -B build/cbench && cmake --build build/cbench \
   && ./build/cbench/throughput                                    # raw C ABI
-dotnet run -c Release --project bindings/csharp/benchmarks        # C# / .NET (P/Invoke)
+dotnet run -c Release --project bindings/csharp/benchmarks        # C# (P/Invoke)
 ( cd bindings/go/benchmarks && go run . )                         # Go (cgo)
 mvn -q -f bindings/java install -DskipTests \
   && mvn -q -f bindings/java/benchmarks exec:exec -Dexec.mainClass=org.wickra.benchmarks.Throughput