[Plonky3 Codegen] Propagate tagging to Plonky3 generated constraints

PR #461 adds a Plonky3 Backend to air-script. It converts air-script programs into AirBuilder equivalent constraints. This issue, along with #534, outlines improvements on this Plonky3 backend that could be useful to better suit the current codebases and needs (e.g. regarding MidenVM constraints generation and comparison).

Since PR #461 was made, the constraints tagging system (https://github.com/0xMiden/air-script/pull/539) made it easier to track constraints and compare air-script constraints with AirBuilder constraints to ensure they are equal.
PRs [#540, and from #543 to #554] (on the air-script side) and [#2725, #2735, #2736 and from #2748 to #2756] (on the miden-vm side) leveraged this tagging system to write MidenVM constraints in both languages.

What would be interesting is to improve the existing Plonky3 backend to support these tags, and be able to directly compare the auto-generated AirBuilder constraints from the manually-written ones.

However, this may be dependent on #534 to improve readability of generated constraints first.

Überprüfe PR #461, um das Plonky3-Backend und das in PR #539 eingeführte Tagging-System zu verstehen. Untersuche die verlinkten PRs auf beiden Seiten (air-script und miden-vm), um zu sehen, wie Tags verwendet werden. Die Arbeit beinhaltet die Änderung des Codegens, um Tags an generierte Constraints weiterzugeben, wahrscheinlich im Plonky3-Backend-Modul. Beginne damit, den Code für die Constraint-Generierung zu lokalisieren und die Tag-Datenstrukturen zu verstehen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.