Feature: storage, database

[xDimon]

This PR add support storages: kv-buffer storage, two implementation: in-memory and rocksdb

[Copilot]

Pull Request Overview

This PR adds support for key–value buffer storage by introducing two storage implementations (in-memory and RocksDB) alongside updates to configuration handling and chain specification parsing.

• Reorder and refactor include directives in logger and formatter files
• Introduce RocksDB storage binding and update database configuration parsing
• Add new chain spec implementation and update CMake configurations

Reviewed Changes

Copilot reviewed 79 out of 79 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/log/logger.cpp	Reorders include directives to reference logger header before other includes
src/log/formatters/variant.hpp	Updates the visit function call to use jam::visit_in_place instead of kagome version
src/injector/node_injector.cpp	Updates storage bindings, switching the default for SpacedStorage to RocksDB
src/app/impl/chain_spec_impl.cpp	Implements chain spec loading; genesis header parsing logs errors without propagating
CMakeLists.txt	Updates C++ extension settings and adds RocksDB package dependency

Comments suppressed due to low confidence (1)

src/log/formatters/variant.hpp:25

• [nitpick] Verify that switching from kagome::visit_in_place to jam::visit_in_place is intentional and that the new reference is correctly defined for this use case.

    return jam::visit_in_place(variant, [&](const auto &value) {

[Copilot]

[nitpick] Since the binding for InMemorySpacedStorage is commented out, consider either removing the commented code or adding a clarifying comment to explain why RocksDb is now the default binding.

Suggested change

	//di::bind<storage::SpacedStorage>.to<storage::InMemorySpacedStorage>(),
	// The binding for InMemorySpacedStorage is commented out because RocksDb is now the default binding for SpacedStorage.
	// RocksDb provides better performance and scalability for production environments, while InMemorySpacedStorage is primarily used for testing or lightweight scenarios.
	// di::bind<storage::SpacedStorage>.to<storage::InMemorySpacedStorage>(),

[turuslan]

Why not "rapidjson"?

[turuslan]

std::map<ByteVec, ByteVec>?

[xDimon]

For SSO

[turuslan]

May use byte2str/str2byte instead of hex/unhex

[turuslan]

Suggested change

	std::map<std::string, ByteVec> entries;
	std::map<ByteVec, ByteVec> entries;

[turuslan]

Should we copy these interfaces from kagome?
E.g. <K, V> are unused (is multi-inheritance convenient?)

[turuslan]

Do you want to provide default in memory cache?
Can components use std::map directly, or interface allows enabling/disabling persistence?
This interface shouldn't be injected, should wrap struct DefaultMemoryCache { shared_ptr<BufferStorage> ptr; }.

Suggested change

di::bind<storage::BufferStorage>.to<storage::InMemoryStorage>(),

[xDimon]

This is used as current light-weight implementation. Developer will use appropriate implementation on demand. I think, BufferStorage should not be used directly.