feat(stark): add support for constraint tracking

We should add support for naming/tagging constraints in the AirBuilder to improve debugging. When a constraint fails, the debug builder currently reports only `"constraint not satisfied at instance {i}, row {r}"` with no indication of which logical rule was violated.

### Upstream work

- https://github.com/Plonky3/Plonky3/pull/1431 adds `NamedAirBuilder` and related debugging improvements
- https://github.com/0xMiden/miden-vm/pull/2856 refactors the Miden VM's constraint tagging approach (replaces the earlier PR #2713)

### Goals

- [ ] Integrate with Plonky3's `NamedAirBuilder` from https://github.com/Plonky3/Plonky3/pull/1431
- [ ] Improve the debug builder in `debug.rs` to report constraint names on failure
- [ ] Ensure zero overhead in production builds

---

Ported from https://github.com/0xMiden/p3-miden/issues/29

The issue involves integrating Plonky3's NamedAirBuilder from the linked PR. Start by reading the debug.rs file to understand current constraint reporting. Examine the upstream PRs to see how constraint tagging is implemented. The goal is to modify the AirBuilder to support naming constraints and update the debug builder to report these names on failure, ensuring no performance impact in production.

由索引模型根据 Issue 内容生成。