feat: stdout logging

[kkovaacs]

Summary

This separates user-visible stdout logging from production telemetry by giving stdout its own filter and moving local-development messages onto user:: log targets.

Changes

• Add separate tracing filters for stdout and OpenTelemetry:
  • MIDEN_STDOUT_FILTER, falling back to RUST_LOG, then info,user=debug
  • MIDEN_OTEL_FILTER, falling back to RUST_LOG, then info,axum::rejection=trace
• Keep stdout formatting compact and focused on user-visible output.
• Add user::... log targets for node, remote prover, validator, block producer, RPC, and store components.
• Move local-development state/action logs to debug! events on user:: targets.
• Keep telemetry-oriented attributes on spans so they remain available to OpenTelemetry exporters.
• Add per-handler RPC spans and record request-derived fields such as account IDs, block ranges, transaction IDs, and reference blocks after parsing.
• Reduce noisy emitted events by moving verbose request payloads and internal details to trace!.
• Remove several verbose ret(level = "debug") instrumented return logs from store queries.
• Clean up block producer and store tracing around block application, transaction input loading, proof scheduling, and RPC/store connectivity.

Notes

The default stdout behavior now shows normal info logs plus user-targeted debug events, without raising debug verbosity for production telemetry. OpenTelemetry keeps its own independent filter so span export behavior can be tuned separately from local console output.

Changelog

[[entry]]
scope       = "general"
impact      = "changed"
description = "Logs printed to standard output have been changed to be human readable. gRPC requests and internal state changes should be now visible."