Support for containerized validators

[ofek-ts]

Hey, in the past we were able to run a validator using docker, but now it seems not - due to the "behind a NAT" error:

INFO validator: validator/src/main.rs:32: Starting Arch-Network Validator...
 INFO validator: validator/src/lib.rs:85: Using peer identity: "16Uiu2HAmEQg4c2LQnpetFDwumK1oaMiyVUyP4yLdGMSvh8zEFyRa"
2024-10-28T19:03:27.582205Z  INFO libp2p_swarm: /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/libp2p-swarm-0.44.2/src/lib.rs:367: local_peer_id=16Uiu2HAmEQg4c2LQnpetFDwumK1oaMiyVUyP4yLdGMSvh8zEFyRa
to bootnode...
024-10-28T19:03:27.585531Z  INFO validator: validator/src/lib.rs:179: Local address: /ip4/0.0.0.0/tcp/29001
2024-10-28T19:03:27.585536Z  INFO validator: validator/src/lib.rs:180: Will listen on TCP port 29001
024-10-28T19:03:27.585537Z  INFO validator: validator/src/lib.rs:182: RPC: 0.0.0.0 9001
thread 'tokio-runtime-worker' panicked at /arch-network/network/src/error.rs:90:13:
Fatal network error: NodeIsBehindNAT
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: network::error::handle_network_error::{{closu
3: validator::p2p::event::event_handler::handle_swarm_event::{{closure}}
4: validator::main_event_loop::{{closure}}::{{closure}}
5: tokio::runtime::task::core::Core<T,S>::poll
6: tokio::runtime::task::harness::Harness<T,S>::poll
7: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
8: tokio::runtime::scheduler::multi_thread::worker::Context::run
9: tokio::runtime::context::runtime::enter_runtime
10: tokio::runtime::scheduler::multi_thread::worker::run
11: tokio::runtime::task::core::Core<T,S>::poll
12: tokio::runtime::task::harness::Harness<T,S>::poll
13: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Using ghcr.io/arch-network/validator:0.2.11