feat(network-monitor): inline .masm scripts as Rust string constants

[Ollie202]

Summary

Closes #1831

• Inlines counter_program.masm as COUNTER_PROGRAM_CODE: &str constant in deploy/counter.rs
• Introduces CounterComponent struct following the IncrNonceAuthComponent pattern from miden-standards, with a LazyLock-compiled Library and a From impl
• Inlines increment_counter.masm as INCREMENT_NOTE_SCRIPT: &str constant in counter.rs
• Deletes the two .masm asset files

The MASM logic is unchanged — only the delivery mechanism changes from external files to Rust constants, improving maintainability and reducing the risk of protocol changes slipping through unnoticed.

Test plan

• CI build and lint pass
• Network monitor boots and counter increments as expected

[Mirko-von-Leipzig]

This just inlines the masm as a string.

The intent of the issue is to write the accounts in rust and then use the Miden rust compiler to compile this to masm.

[Ollie202]

Closing — misunderstood the intent. Will reimplement using the Miden Rust compiler to compile Rust account code to MASM rather than just inlining the existing MASM as strings.

[Ollie202]

Thanks for the clarification. I dug into the #[component] proc macro approach from the miden crate (the 0xMiden/project-template shows the pattern nicely), where you compile Rust to MASM via cargo miden build and load it with AccountComponent::from_package().

The issue I ran into is that AccountComponent::from_package() doesn't seem to exist in miden-protocol v0.14, which is what this repo currently depends on. It looks like it lives in the miden-client stack rather than here.

So I wanted to check before going further:

1. Does this need the new toolchain (miden crate, cargo-miden, from_package API) integrated into the node's dependencies first?
2. Or is there a different approach you had in mind that works within the current dependency set?

Happy to go whichever route makes sense.