[Feature] Use ControlBus to Restart Perfomers after Unacceptable Message Limit Hit

[iancooper]

Is your feature request related to a problem? Please describe.
If you use send a PATCH to reduce the performers to 0, and then send another PATCH to update performers to 1, it works as expected.

However, if the number of performers went down to 0 automatically because the unacceptable message limit has been reached, sending a PATCH with performers of 1 doesn't seem to work. The performers remain at 0.

Describe the solution you'd like
After the unacceptable message limit has been reached, it is possible to use PATCH to override the shutdown of a performer and start a new one.

Describe alternatives you've considered
You could just restart the app, but in some cases this is expensive by comparison to just restarting the performer, so it would be nice to be able to adjust this. If we really wanted the unacceptable message limit to crash and for