Feat/api daemon

[zeroXbrock]

Motivation

Manage multiple [long-running] scenarios remotely.

Solution

Host a JSON-RPC server that manages contender sessions.

• log streaming over WS or SSE
• per-session seeds to prevent accidental tx/nonce conflicts
• spam a scenario multiple times w/o repeating funding/setup
• RPC methods: add_session, get_session, spam, stop, remove_session

TODO:

• add an endpoint to fund the spammers
• add a keystore to the server; enable multiple users to fund accounts simultaneously (currently relying on one key for all funding, which also causes conflicts when initializing multiple scenarios at once (calling add_session))
• maybe more endpoints? What else about the scenario/spammer would we like to control?

PR Checklist

• Added Tests
• Added Documentation
• Ran cargo +nightly clippy --workspace --lib --examples --tests --benches --all-features --locked --fix
• Ran cargo fmt --all
• Note breaking changes in PR description, if applicable
• update changelogs
  • Update CHANGELOG.md in each affected crate
  • add a high-level description in the root changelog