feat: Validator binary crate, Dockerfile, and Debian package

[sergerad]

Relates to #1961.

➜ ./target/debug/miden-validator -h
Miden validator binary

Usage: miden-validator <COMMAND>

Commands:
  bootstrap  Bootstraps the genesis block
  start      Starts the validator component
  help       Print this message or the help of the given subcommand(s)

[sergerad]

Debian workflow works until release is required, as expected https://github.com/0xMiden/node/actions/runs/25411348891

[Mirko-von-Leipzig]

I didn't audit the old/moved code in depth, I assume its largely a copy-paste operation.

[Mirko-von-Leipzig]

This will come up a bunch. Should we create separate "base images" for building and runtime?

[kkovaacs]

As far as I understand that's not possible without using some extensions. We could add dockerfile-x though and move the builder and runner image definitions to a common Dockerfile referenced by the per-service Dockerfiles.

[sergerad]

I have gone with a merged Dockerfile with ARGs for bin and port. Might not be flexible enough for us in the end, but it might be (same will work fine for the ntx-builder image).

[Mirko-von-Leipzig]

Lets see how it goes. I don't like that it assumes the binaries are the same and can be coupled like this.

I think what I was assuming originally is that we would publish build and runtime base images. I don't understand why that isn't possible; isn't that how

FROM rust:1.93-slim-bookworm AS chef

exist?

[Mirko-von-Leipzig]

I would really like if we could get rid of these. They're a pain to maintain.

I guess this could be done in tandem with removing Debian packages once we move to docker ourselves?

[kkovaacs]

Just two comments:

• bin/genesis/README.md still has a reference to miden-node validator bootstrap which is now gone.
• Similarly, scripts/run-node.sh still tries to bootstrap with miden-node validator bootstrap, so it's effectively broken.

[bobbinth]

I think I saw a comment from @Mirko-von-Leipzig regarding naming somewhere: it does feel strange to have both miden-node-validator and miden-validator crates.

One potential option is to have both library and binary targets in the miden-node-validator crate - but I'm not sure if that's a good idea.