Update intent-gizmosql to GizmoSQL v1.38.0-intent.2 and DuckDB v1.5.5-intent.2 - #2349

Updates intent-gizmosql to new releases of its two forks: GizmoSQL v1.38.0, the same server as the existing gizmosql entry, with server and client changes, and its embedded DuckDB v1.5.5 with engine changes.

Source and release

• https://github.com/bddppqs/intent-gizmosql, tag v1.38.0-intent.2: the release this entry installs (portable Linux amd64 and arm64 builds, glibc 2.28 baseline, SHA256SUMS attached); changes in its CHANGELOG.md and CLICKBENCH-FORK.md.
• https://github.com/bddppqs/intent-duckdb, tag v1.5.5-intent.2: the DuckDB changes, described in that repository's CLICKBENCH-FORK.md.
• Both repositories keep their upstream licenses (Apache-2.0 / MIT).

Relation to the gizmosql entry

• Every script is the upstream gizmosql entry's except install, query and util.sh (the README says how); the schema (create.sql) and load path are upstream's; no index, pre-aggregation or query-specific setting.

Disclosure and labels

• Release 2 continues the engine work of release 1 and keeps its tuned: yes label, for the reasons the README states. If you prefer a different name or tag, please relabel it.
• Since release 1: above 64 CPUs util.sh sets DuckDB threads to half the CPUs and allocator settings (not suggested defaults), and new database files created at the latest storage version, as the entry's are, use zstd-compressed blocks under the fork's own storage version; the README states both.

Reproduction

• No result file is included; the entry's current results are release 1's, for your runs to replace. We ran benchmark.sh unattended by cloud-init on a fresh c8g.metal-48xl (Ubuntu 24.04), no manual steps; could you run it with machine:all?