feat(Prover CLI): `restart` cmd rework

[ilitteri]

What ❔

Reworks the restart cmd implementation to accept a subcommand as an argument. Instead of having --batch and --job to differentiate between whether you'd want to restart a given batch from the beginning or whether you want to restart a specific job (re-queue it), now they're separated into two different subcommands batch and job.

In this PR, I introduce the implementation of restart batch, with which a user can restart the proof of a batch from any stage by passing the correct flag.

restart batch cmd flags:

• --bwg, --basic-witness-generator. Restarts a batch from the basic witness generator stage (wiping the subsequent stages' data and re-queuing the witness inputs jobs).
• --lwg, --leaf-witness-generator. Restarts a batch from the leaf witness generator stage (wiping the subsequent stages' data and re-queuing the leaf aggregation round jobs).
• --nwg, --node-witness-generator. Restarts a batch from the node witness generator stage (wiping the subsequent stages' data and re-queuing the node aggregation round jobs).
• --rt, --recursion-tip. Restarts a batch from the recursion tip stage (wiping the subsequent stages' data and re-queuing the recursion tip jobs).
• -s, --scheduler. Restarts a batch from the scheduler (wiping the subsequent stages' data and re-queuing the scheduler jobs).
• -c, --compressor. Restarts the compressor job for the given batch.

Why ❔

For a user to restart the proof of a given batch from any process stage.

Checklist

• [x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
• [ ] Tests for the changes have been added / updated.
• [x] Documentation comments have been added / updated.
• [x] Code has been formatted via zk fmt and zk lint.
• [x] Spellcheck has been run via zk spellcheck.