Add aggregator toggle API and fix single proof pass-throug

[bomanaps]

leanEthereum/leanMetrics#30
leanEthereum/leanSpec#636
and single proof fix

[ArtiomTr]

also looks like CI fails, as code is not formatted

[ArtiomTr]

I think there is no need to define helper that is used only in one place - just use it directly in test

[ArtiomTr]

you can just use .expect here

[ArtiomTr]

you can avoid creating tokio runtime by hand, by using tokio::test macro

[ArtiomTr]

I think there is no need to use real tcp socket for testing - you can just use axum router directly, as shown in their examples, i.e. https://github.com/tokio-rs/axum/blob/de9f13d809e86f8bf24292aac0af16d97ef91195/examples/testing/src/main.rs#L68

[ArtiomTr]

I think there is no need to add formatting / logging to these - the cargo will automatically report results

[ArtiomTr]

probably no need to print this info

[ArtiomTr]

I think it would be better if this is also defined as a struct, not via json! macro

[ArtiomTr]

this probably should be this instead:

Suggested change

	body: Result<Json<ToggleRequest>, JsonRejection>,
	Json(body): Json<ToggleRequest>,

so you don't have to handle BAD_REQUEST error code yourself.

[ArtiomTr]

I would probably unified the default values accross both Default trait and clap:

#[derive(Debug, Clone, Args)]
pub struct HttpServerConfig {
    #[clap(long = "http-address", default_value_t = HttpServerConfig::default().http_address)]
    http_address: IpAddr,

    #[clap(long = "http-port", default_value_t = HttpServerConfig::default().http_port)]
    http_port: u16,
}

to keep those in single place

[ArtiomTr]

I think this is not a good idea, to expose crate internals to outside world - you should export only needed parts via pub use instead. If some internals are needed for testing, then probably it is a good idea to move tests into the same file as internals, not to expose them.