E2E tests runner refactor. Use `clap` and `anyhow`

[josecelano]

I'm using clap and anyhow in all binaries because the configuration is getting more complex.

Allow to inject the tracker configuration with env vars.

Currently, you can run it like this:

cargo run --bin e2e_tests_runner "./share/default/config/tracker.e2e.container.sqlite3.toml"

But it would be also interesting to run it with:

TORRUST_TRACKER_CONFIG=[value] cargo run --bin e2e_tests_runner

or:

TORRUST_TRACKER_PATH_CONFIG="./share/default/config/tracker.e2e.container.sqlite3.toml" cargo run --bin e2e_tests_runner

Subtasks

• Migrate to clap and anyhow.
• Allow injecting config with env vars.

cc @da2ce7

[da2ce7]

@josecelano I'm supportive of generally moving to clap and anyhow, for all of our projects.

[josecelano]

Finally, you can execute it with:

cargo run --bin e2e_tests_runner -- --config-toml-path "./share/default/config/tracker.e2e.container.sqlite3.toml"

Or:

TORRUST_TRACKER_CONFIG_TOML_PATH="./share/default/config/tracker.e2e.container.sqlite3.toml" cargo run --bin e2e_tests_runner

Or:

TORRUST_TRACKER_CONFIG_TOML=$(cat "./share/default/config/tracker.e2e.container.sqlite3.toml") cargo run --bin e2e_tests_runner