docs(dremio): correct false Flight client auto-retry claim in deployment guide The Dremio deployment guide stated transient gRPC errors 'rely on the Flight client's default retry policy' and that the 'Flight client auto-retries'. The shared flight_client crate (crates/flight_client) implements no retry/backoff/reconnect logic — on connection reset it returns Error::ConnectionReset whose message asks the *caller* to retry (crates/flight_client/src/lib.rs:177-178), and the channel is built with a plain tonic .connect() (arrow_flight_factory.rs) with no retry layer. Transient errors surface to the caller. Corrected both the Resilience Controls prose and the troubleshooting table row. Verified against spiceai/spiceai trunk @ d9ad5df96.

Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>