Bump icebird to 0.8.19 for string bounds pruning (#717)

icebird 0.8.18 (hyparam/icebird#35) admits string/binary/uuid/fixed
columns to Iceberg manifest bounds pruning. Truncation keeps those
bounds valid as outer bounds, so a skip that requires the predicate to
be provably outside [lo, hi] stays sound; $ne/$nin still never prune.

This matters here twice. Locally, a date-scoped query over recorded
cache tables can now skip whole files instead of opening every one. In
hypaware-server's deployed image the two packages install separate
trees, so the cache tier resolves THIS pin while the archive tier
resolves the server's - the server bumped in hyparam/hypaware-server#326
and the cache tier stayed on 0.8.17 until this.

The same release also orders strings by code point rather than UTF-16
code units, which is the order Iceberg specifies for bounds and sort
keys. That corrects min/max bound selection and write-path sorting for
strings mixing U+E000..U+FFFF with supplementary characters; ASCII and
common text are unaffected.

Author: philcunliffe

package.json

@@ -71,7 +71,7 @@
     "@aws-sdk/credential-provider-ini": "3.973.12",
     "hyparquet": "1.28.1",
     "hyparquet-compressors": "1.1.1",
-    "icebird": "0.8.17",
+    "icebird": "0.8.19",
     "marked": "18.0.9",
     "squirreling": "0.15.0"
   },