[branch-56] Prepare for 56.0.0 release: Version and Changelog - #27098

…to 0.14 (#1616)

Part of #1366. This doesn't close it yet: the 13 zstd 0.13 IDs stay in
`.cargo/audit.toml`.

## What moved

- Reliaburger's own `zstd` dependency and build dependency (source
bundle, #1570): 0.13 -> 0.14.3.
- `include-flate`, `include-flate-codegen`, `include-flate-compress`
(through rust-embed's `compression`): 0.3.4 -> 0.3.5, which requires
zstd `^0.14`. A `Cargo.lock` update only.

`cargo tree -i [email protected] -e normal,build --depth 1` now lists only
`arrow-ipc` 59.3.2, `parquet` 59.3.2, `datafusion` 55.2.0 and
`datafusion-datasource` 55.2.0.

## Why the ignores stay

Parquet and arrow-ipc 59.3.2 (the newest 59 release) require zstd
`^0.13`. Arrow 60 moves to 0.14, but DataFusion 55.2.0, still the newest
on crates.io, requires arrow `^59.2`. Log Parquet is written with zstd,
so turning the codec off isn't an option. DataFusion 56.0.0
(arrow/parquet 60.1, zstd 0.14) has `branch-56` cut and its version PR
(apache/datafusion#27098) open since 4 November, but the vote and the
crates.io publish haven't happened yet (apache/datafusion#24461). The
upgrade guide suggests a small move for us: MSRV 1.95, object_store 0.14
(already ours), arrow's `Metadata` type, and
`TableProvider::scan_with_args` gaining a defaulted `skip`.

## Nothing durable changed

Both zstd lines link the one `zstd-sys` 2.1.2 (libzstd 1.5.7), so the
source bundle compresses the same way at the same levels. Log and metric
Parquet still goes through Parquet's own codec, which this doesn't
touch. No `CURRENT` bump.

## Also

- New test `only_arrow_parquet_and_datafusion_still_lock_zstd_0_13` in
`tests/suite/dependency_audit.rs`.
- New record `docs/qualification/2026-11-06-dependency-exceptions.md`,
linked from `docs/testing.md`. The `.cargo/audit.toml` comment is
updated.
- Book chapter 06 tells the zstd part of the arrow story.

`make ci` is clean, including fmt and clippy `-D warnings`. No export
code changed, so `make test-s3` wasn't run.

## Which issue does this PR close?

- Part of #24461

## Rationale for this change

Several PRs were backported to `branch-56` after the changelog was
generated in #27098, so they
are missing from `dev/changelog/56.0.0.md`.

## What changes are included in this PR?

Regenerates the changelog with `dev/release/generate-changelog.py 55.0.0
branch-56 56.0.0`. This adds entries for:

- #27243
- #27204
- #27331
- #27369
- #27368
- #27098

and updates the commit count and credits.

## What is the testing strategy for this PR?

N/A (changelog only)

## Are there any user-facing changes?

No

Co-authored-by: Claude Fable 5.2 <[email protected]>