Use bps.monitor and baseline_wrapper instead of our read hardware plans

[797](https://github.com/DiamondLightSource/mx-bluesky/pull/797) Introduced some changes to our `read_hardware` plans. Instead of using a plan to read hardware once before collection and once after collection, we should use https://nsls-ii.github.io/bluesky.plans.baseline_wrapper.html to get initial device readings and https://blueskyproject.io/bluesky/main/generated/bluesky.plan_stubs.monitor.html#bluesky.plan_stubs.monitor throughout the plan.

This feels cleaner and the monitor will give us more information than a single read during collection

## Acceptance Criteria
- The above bluesky functions used in place of our own manual `read_hardware_plan`