Fix Linux release DuckDB link

[wesm]

Summary

• Build Linux release artifacts in Ubuntu 22.04 so DuckDB 1.5.4's prebuilt static libraries link against a compatible C++ runtime.
• Log both GLIBC and GLIBCXX runtime requirements in release builds.

Test Plan

• Reproduced the Ubuntu 20.04 Linux amd64 link failure locally.
• Built and smoke-tested Linux amd64 in Ubuntu 22.04.
• Built and smoke-tested Linux arm64 in Ubuntu 22.04.
• Ran git diff --check HEAD~1..HEAD.

[roborev-ci]

roborev: Combined Review (d27a822)

Summary verdict: One medium release compatibility risk remains; no high or critical issues were reported.

Medium

• .github/workflows/release.yml:25 - Building the generic Linux release inside ubuntu:22.04 can raise the runtime glibc/libstdc++ baseline for msgvault_linux_* artifacts, while the installer still downloads only by OS/arch and does not enforce a minimum distro/runtime. Users on older Linux systems may receive a binary that cannot start.
  Fix: Build Linux releases against the oldest supported runtime, or explicitly raise and enforce the minimum Linux runtime in docs/installer checks. If DuckDB needs newer C++ symbols, consider statically linking or bundling the C++ runtime and add a failing compatibility threshold instead of only printing versions.

---

Panel: ci_default_security | Synthesis: codex, 7s | Members: codex_default (codex/default, done, 1m26s), codex_security (codex/security, done, 8s) | Total: 1m41s

[roborev-ci]

roborev: Combined Review (8a86792)

No issues found.

---

Panel: ci_default_security | Synthesis: codex | Members: codex_default (codex/default, done, 3m28s), codex_security (codex/security, done, 1m0s) | Total: 4m28s

[sweenzor]

I broke this in #390, sorry about that!