HDF5 2.0 native complex as a first-class type on read; Python libver=

- Datatype::parse returns Datatype::Complex for class 11 (also inside
  compounds, arrays and VL types) instead of the {r, i} compound view.
- Facade: DType::Complex(Box<DType>); read_complex_f32/f64 accept it.
- h5rs dump/ls/diff print native complex as h5dump/h5ls/h5diff 2.2.0 do
  (checked against a fixture written by h5py 3.16 / libhdf5 2.0.0);
  dump --json keeps the {r, i} compound (hdf5-json has no complex class).
- clawhdf5-wasm reads native complex datasets as [re, im] pairs.
- Python: clawhdf5.File(path, 'w', libver=...) with h5py's values,
  mapped to FileBuilder::libver_bounds; 'v108' output opens in HDF5 1.8.23.
- Docs: known-issues entry moved to Fixed (history), CHANGELOG, READMEs.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

examples/wasm-viewer/test/test.mjs

@@ -399,7 +399,7 @@ async function remoteTests() {
   await fails(async () => {
     const f = await pkg.openUrl(`${base}/fix/fixture.h5`, {
       blockSize: 512,
-      fetch: tamper(async (r) => withHeaders(r, { "Content-Range": "bytes 0-511/25752" })),
+      fetch: tamper(async (r) => withHeaders(r, { "Content-Range": `bytes 0-511/${statSync(join(fixDir, "fixture.h5")).size}` })),
     });
     await f.read("/grid");
   }, /the server sent 0-511/, "wrong range");
@@ -550,7 +550,7 @@ async function floodTests() {
       const range = new Headers(init.headers).get("Range");
       if (range === "bytes=0-511") return fetch(url, init);
       const m = /^bytes=(\d+)-(\d+)$/.exec(range);
-      return new Response(f.body, { status: 206, headers: { "Content-Range": `bytes ${m[1]}-${m[2]}/25752` } });
+      return new Response(f.body, { status: 206, headers: { "Content-Range": `bytes ${m[1]}-${m[2]}/${statSync(join(fixDir, "fixture.h5")).size}` } });
     },
   }).catch((e) => e);
   // The open itself may need a second range: flooded either way.