cli: Restart container if error is raised by benchmark

In the happy path we aim to avoid tearing down and restarting the
container between repeats of the same benchmark to speed up execution
time. But if there was an error on a previous run, let's force restart
the container to clean up any bad state that was left behind.

Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>