chore(deps): bump nodedb-client/types to 0.4.0

[laksamanakeris]

Bumps nodedb-client / nodedb-types from 0.3.0 to 0.4.0 (plus transitive nodedb-codec 0.4.0, zerompk 0.6.1).

No source changes required. Only services/error.rs and one mock error construction touch client types, because the client stays isolated behind the ConnectionService seam.

Compatibility

The compatibility target is now deliberately split: server 0.5.0, client 0.4.0. NodeDB server 0.5.0 shipped 2026-08-04 but published no crates, so 0.4.0 is the only client available.

Verified compatible across the v0.4.0/v0.5.0 tags, then confirmed at runtime against a server built from the v0.5.0 tag and driven by this exact client:

Check	Result
PROTO_VERSION / _MIN	both still 1
OpCode variants	unchanged
Handshake auth	0.5.0 dropped the server-side Trust username default; the client cannot emit the rejected frame since native/builder.rs:112 always populates it
New wire field FID_VECTOR_DIM = 90	skipped by the client's unknown-field arm (text_fields/decode.rs:344)
Live smoke test	ping OK, capabilities() = 0x7f, DDL and DML round-trip

What 0.4 actually adds

list_insert, list_delete, list_move (CRDT list ops). Nothing removed.

It closes none of the known client-side gaps: SearchResult.metadata and SubGraph properties still decode empty, pooled begin/commit/rollback still acquire different connections, results are still fully buffered with no cursor, and there is still no close() or connection-state observability. The unpublished 0.5 client closes none of them either.

So this bump is about staying current and unblocking the verified server-0.5.0 target, not about new capability.

Verification

cargo fmt --all --check                                                # clean
cargo clippy --workspace --all-targets --all-features -- -D warnings   # clean
cargo nextest run                                                      # 60 passed, 0 skipped