Agnostic_baker: Add --with-accuser option to run accuser

What

Closes #7910 (closed).

Why

How

By adding the Accuser underlying run function as asynchronous in the Baking_commands module.

Manually testing the MR

By running a node and then the agnostic baker with the --with-accuser command:

$ ./octez-baker --base-dir ~/.tezos-client-ghostnet --endpoint http://localhost:18733 run with local node ~/.tezos-node-ghostnet --liquidity-baking-toggle-vote pass --without-dal --with-accuser --preserved-levels 50

May 01 17:13:26.890 NOTICE │ agnostic baker started
May 01 17:13:26.893 NOTICE │ starting baker for protocol PsRiotumaAMo
May 01 17:13:27.030 NOTICE │ baker for protocol PsRiotumaAMo is now running
May 01 17:13:27.033 NOTICE │ read liquidity baking toggle vote = pass
May 01 17:13:27.033 NOTICE │ read adaptive issuance vote = pass
May 01 17:13:27.034   WARN │ No DAL node endpoint has been provided.
May 01 17:13:27.034   WARN │ Not running a DAL node might result in losing a share of the participation
May 01 17:13:27.034   WARN │   rewards.
May 01 17:13:27.034   WARN │ For instructions on how to run a DAL node, please visit https://docs.tezos.com/tutorials/join-dal-baker.
Node is bootstrapped.
Waiting for protocol 022-PsRiotum to start...
Node is bootstrapped.
Waiting for protocol 022-PsRiotum to start...
May 01 17:13:27.035 NOTICE │ new block (BLBWsvSUcZtduRZ4g8b4LaAowwk6u2D6udiWsEWQvoae5kpHqXf) on proposal period (remaining period duration 2507)
Accuser 21.0~rc3+dev (c325f770) for PsRiotumaAMo started.
pre-emptive-forge-time optimization set to 0.600000s. Operation inclusion window is ~3.400000s. Caution: Setting this too high may result in reduced block proposal rewards.
Baker 21.0~rc3+dev (c325f770) for PsRiotumaAMo started.
May 01 17:13:27.038 NOTICE │ Baker will run with the following delegates:
May 01 17:13:27.038 NOTICE │
May 01 17:13:27.044   WARN │ initializing irmin context at /Users/gabrielmoise/.tezos-node-ghostnet/context
May 01 17:13:27.146 NOTICE │ successfully migrated nonces: legacy nonces are safe to delete
May 01 17:13:27.146 NOTICE │ received new head BLBWsvSUcZtduRZ4g8b4LaAowwk6u2D6udiWsEWQvoae5kpHqXf at level 12174741, round 0
May 01 17:13:28.149 NOTICE │ received new proposal BMcS8jwHB4s19QvsC9QVgBLoVfYg7WFNy7MbWvgTj2ioN5oqitM at level 12174742, round 0
May 01 17:13:28.159   WARN │ No DAL node endpoint has been provided.
May 01 17:13:28.159   WARN │ Not running a DAL node might result in losing a share of the participation
May 01 17:13:28.159   WARN │   rewards.
May 01 17:13:28.159   WARN │ For instructions on how to run a DAL node, please visit https://docs.tezos.com/tutorials/join-dal-baker.
May 01 17:13:28.179 NOTICE │ received new head BMcS8jwHB4s19QvsC9QVgBLoVfYg7WFNy7MbWvgTj2ioN5oqitM at level 12174742, round 0
May 01 17:13:28.182 NOTICE │ new block (BMcS8jwHB4s19QvsC9QVgBLoVfYg7WFNy7MbWvgTj2ioN5oqitM) on proposal period (remaining period duration 2506)
May 01 17:13:28.191 NOTICE │ block BMcS8jwHB4s19QvsC9QVgBLoVfYg7WFNy7MbWvgTj2ioN5oqitM registered
May 01 17:13:32.492 NOTICE │ received new proposal BMBWoCrk97icTUMjvRjWTukGmYojqSA8iNzFvAxXPZ9zEZFYG1S at level 12174743, round 0
May 01 17:13:32.514 NOTICE │ received new head BMBWoCrk97icTUMjvRjWTukGmYojqSA8iNzFvAxXPZ9zEZFYG1S at level 12174743, round 0
May 01 17:13:32.517 NOTICE │ block BMBWoCrk97icTUMjvRjWTukGmYojqSA8iNzFvAxXPZ9zEZFYG1S registered
May 01 17:13:32.518 NOTICE │ new block (BMBWoCrk97icTUMjvRjWTukGmYojqSA8iNzFvAxXPZ9zEZFYG1S) on proposal period (remaining period duration 2505)
...

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR