feat: database crate

[heilhead]

Description

This adds wcn_db crate for a standalone database server binary.

How Has This Been Tested?

Existing tests and some new ones.

Due Diligence

• Breaking change
• Requires a documentation update
• Requires a e2e/integration test update

[Copilot]

Pull Request Overview

Adds a new wcn_db crate to provide a standalone database server binary and migrates existing code to use the new wcn_rocks and wcn_logging crates.
Key changes:

• Swapped out relay_rocks for wcn_rocks across node and storage layers, and updated TTL methods from exp/setexp/hexp/hsetexp to get_exp/set_exp/hget_exp/hset_exp.
• Renamed error payload fields from details to message with with_message builder methods.
• Introduced convenience impls (from_bytes/as_bytes, from_unix_timestamp_*, to_unix_timestamp_*) for Namespace, RecordExpiration, and RecordVersion.

Reviewed Changes

Copilot reviewed 43 out of 44 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
crates/rpc/src/quic/client.rs	Bug in named-format usage for format!.
crates/storage_api2/src/rpc/mod.rs	Renamed RPC error field details → message.
crates/rocks/src/db/types/common/iterators.rs	Renamed has_more → has_next in scan result.
crates/wcn/src/commands/node/{stop.rs,start.rs,mod.rs}	Updated logger import to wcn_logging.
crates/rocks/src/db/types/{string.rs,map.rs,mod.rs}	Unified Record and MapRecord types and renamed methods.

Comments suppressed due to low confidence (3)

crates/storage_api2/src/rpc/mod.rs:159

• Changing the serialized field name from details to message is a breaking change for RPC clients. Consider adding a #[serde(rename = "details")] or #[serde(alias = "details")] on message to maintain backward compatibility.

    message: Option<String>,

crates/rocks/src/db/types/common/iterators.rs:48

• Renaming the scan result field has_more to has_next changes the public API. Ensure consumers are updated and consider deprecating the old field or documenting the rename.

    pub has_next: bool,

crates/rpc/src/quic/client.rs:198

• Using named braces inside format! without supplying named arguments will fail to compile. Either switch back to positional formatting ("... {} ... {}", peer_id, actual_peer_id) or use named parameters (format!("... {peer_id} ... {actual_peer_id}", peer_id=peer_id, actual_peer_id=actual_peer_id)).

                    "Invalid peer ID: expected: {peer_id} actual: {actual_peer_id}"

[nopestack]

consider making these default values constants instead.

[heilhead]

That would be inconsistent with other crates. If we decide to change the way we initialize these configs, we should update all of the binary crates that initialize this way.

[nopestack]

it can be done progressively though, minor nit though

[xDarksome]

We already discussed that multiple times @nopestack and agreed that if the var is being used in one place only it's fine to inline it