feat(metrics): implement new metric groups for consumer and smart-rou…

…ter (lavanet#2238)

feat: bump target version to 6.1.0 (lavanet#2234)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

feat: Bump protocol version to v6.0.1 (lavanet#2233)

feat: bump target version to 6.0.0 (lavanet#2230)

Co-authored-by: Cursor <cursoragent@cursor.com>

feat: support multiple --use-static-spec sources with aggregation (la…

…vanet#2225)

Allow --use-static-spec flag to be specified multiple times, aggregating
specs from local files, directories, GitHub, and GitLab repositories.
When the same chain ID appears in multiple sources, the later source
completely replaces the earlier spec (full replacement, not merge).

Changes:
- Change --use-static-spec from String to StringArray flag type
- Add spec aggregation logic with last-wins override semantics
- Support comma-separated local file paths (file1.json,file2.json)
- Add helper functions for loading all specs from various sources
- Add comprehensive tests for aggregation behavior
- Remove unused GetSpecsFromPath function

Multiple local files can be specified either as separate flags or comma-separated:
  --use-static-spec file1.json --use-static-spec file2.json
  --use-static-spec file1.json,file2.json

Co-authored-by: Cursor <cursoragent@cursor.com>

fix(chainlib): include response error in ID mismatch logs (lavanet#2192)

When a node returns an error (e.g., "Apikey is expired") with an
empty/invalid JSON-RPC ID, the ID validation fails with a confusing
parsing error. This adds the actual response error message to the
log output, making the root cause immediately visible.

target-version 5.6.1->5.6.2 (lavanet#2142)

bump min and target version (lavanet#2141)

fix(resource_limiter): batches are going to heavy bucket instead of n…

…ormal one (lavanet#2140)

feat: update protocol version to 5.5.1 (lavanet#2106)

* adding upgrader

* update version to 5.5.1

* migration to change TARGET_VALUE onchain value

* adding testing for 24h cooldown period