Add configuration option to disable status updates via message bus

[callumforrester]

As well as data documents, blueapi produces events when the status objects monitored by the run engine are updated. These events are useful for creating progress bars and similar updates. Unfortunately it seems very easy to unintentionally make plans/devices produce a very large number of these updates. The handling of all of these results in log spam and high CPU usage.

We're seeing this now on I22 and have seen similar problems before (see #111). I think the easy way to make debugging easier is to make the status update handling optional and easy to turn off via config. To that end...

Changes:

• Add config option to disable status events
• Make the worker only hook into the run engine if this option is marked as true

[codecov]

Codecov Report

Merging #331 (33d9010) into main (8151ca1) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #331      +/-   ##
==========================================
+ Coverage   86.57%   86.61%   +0.04%     
==========================================
  Files          41       41              
  Lines        1549     1554       +5     
==========================================
+ Hits         1341     1346       +5     
  Misses        208      208              

Files	Coverage Δ
src/blueapi/config.py	97.10% <100.00%> (+0.13%)	⬆️
src/blueapi/service/handler.py	84.12% <100.00%> (ø)
src/blueapi/worker/reworker.py	94.44% <100.00%> (+0.04%)	⬆️

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

[rosesyrett]

Looks good; thanks for doing this. Am I alright to merge it in, make a release and try see if that fixes the problems we are seeing on i22?