feat: add custom tracing macro to use reports

[drahnr]

Ref #1406

Adds a miden-node-tracing crate and the inner proc macro impl crate.

The name instrument_with_err_report is suboptimal, open to suggestions or if we want to replace tracing::instrument completely and enhance our instrument_with.. to also handly anyhow errors?

Problem: High cardinality key-spaces slow the backend down

account_id vs account.id make it
a) very hard to find what you need in the honeycomb UI
b) create two different time series which means a cardinality bump

Trimmed UI

tracing::instrument is rather verbose with its key-value style attributes, we only ever use a subset, i.e. we never re-parent spans, but only use parent = None to define a new root span.

Impl

The allowlist controls field keys only — the names on the left-hand side of key = value pairs inside a span or event. It has nothing to do with function names, component names, or span names.

Concretely:

#[instrument(rpc: account.id = %id)]
//           ^^^  ^^^^^^^^^^   ^^^
//           │    │             └─ value  – unrestricted, any _expression_
//           │    └─ field key   – _must_ be in `./allowlist.txt` - this prevents the cardinality bump and accidental key mismatches
//           └─ component    – must be an identifier (const `COMPONENT` or `"string"`

• Component (rpc:, store:, "block-producer":) — becomes the tracing target
• Function name — derived from the Rust function name by tracing::instrument, or overridden via name = "...". Not touched by this macro at all
• Field keys (account.id, block.number, nullifier.id) — the only thing checked against the accountlist.

Details

The PR takes tracing::instrument and tracing::log and wraps them with a custom front-end. If a user provides an unknown key which does not exist verbatim in the allowlist.txt, we do error out and yield a small number of possible alternatives based on some character distance.

See full examples in crates/tracing/tests/ui/pass/instrument.rs

[drahnr]

Open questions: Do we want to prefix the function name with the component in the otel? I.e. component.fnname is always constructed and would allow to scope functions by declared component.