chore: bump bincode-next 3.0.0-rc.13 to 3.0.0-rc.14

[dobby-coder]

Patch bump for the bincode-next rc. From the dep-update scan in #190.

Changes

• pg-core/Cargo.toml: bincode-next 3.0.0-rc.13 → 3.0.0-rc.14
• pg-pkg/Cargo.toml: same
• Cargo.lock refreshed via cargo update -p bincode-next

Verification

• cargo build --workspace — clean (3m03s, host toolchain)
• cargo test --manifest-path pg-core/Cargo.toml --features test,rust,stream — 51 unit tests + 3 doctests pass, including bincode_compat::tests::legacy_config_matches_v1_default_bytes which pins the v1-default byte layout used for on-disk IBS keys in pg-pkg → wire format is unchanged
• cargo test --manifest-path pg-{ffi,pkg,cli}/Cargo.toml --all-features — 1 / 30 / 7 tests pass respectively
• cargo fmt --all -- --check — clean
• cargo audit — clean (444 crates scanned, 0 vulnerabilities)
• bincode-next 3.0.0-rc.14 declares rust-version = 1.91.1, same as rc.13 → no Dockerfile/toolchain change needed

Trust caveat (unchanged)

bincode-next remains the third-party fork by Apich-Organization / panayang, not the original bincode-org. Same caveat as PR #182. If maintainer prefers the audit-allowlist or postcard route, this PR can be closed without harm.

Major bumps deferred

Per #190 the rand 0.8 → 0.10, inquire 0.6 → 0.9, and reqwest 0.11 → 0.13 bumps are out of scope here; a tracker comment will go on #190 once this PR is open.

Reviewer quickstart

git fetch origin && git checkout chore/bincode-next-rc14 && cargo build --workspace && cargo test --manifest-path pg-core/Cargo.toml --features test,rust,stream

Closes #190

[dobby-coder]

Self-review (bot cannot self-approve):

Patch bump only (rc.13 → rc.14) across pg-core, pg-pkg, and Cargo.lock. Diff matches PR body exactly, no other surface touched.

• All CI green across both arches, all workspace test/format jobs, and wasm browsers.
• Wire-format pin (bincode_compat::tests::legacy_config_matches_v1_default_bytes) passes, so on-disk IBS key compatibility is preserved.
• Same upstream trust caveat as #182 — third-party fork — unchanged here.

LGTM from this agent's perspective; needs a human reviewer to actually approve.