891 read flux tranmission put into ispyb during collection

[5u6in]

Fixes #891

1. Split reading hardware into two event streams; read_hardware_for_ispyb_pre_collection and read_hardware_for_ispyb_during_collection and subsequently modifying and adding new code in order to fix various tests.

2. Merge conflicts fixed and tests pass accordingly after updating the venv dependencies.

To test:

1. Run tests

[5u6in]

I am attempting to resolve the conflicts by using git merge main/origin in the terminal in order to use VSCode's merge editor

[codecov]

Codecov Report

Merging #937 (6e0c594) into main (ed29f84) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #937      +/-   ##
==========================================
- Coverage   93.33%   93.31%   -0.02%     
==========================================
  Files          52       52              
  Lines        2506     2514       +8     
==========================================
+ Hits         2339     2346       +7     
- Misses        167      168       +1     

Files	Coverage Δ
...rion/device_setup_plans/read_hardware_for_setup.py	100.00% <100.00%> (ø)
...erion/experiment_plans/flyscan_xray_centre_plan.py	91.78% <100.00%> (+0.05%)	⬆️
...rc/hyperion/experiment_plans/rotation_scan_plan.py	99.12% <100.00%> (+<0.01%)	⬆️
...ernal_interaction/callbacks/ispyb_callback_base.py	92.30% <100.00%> (+0.15%)	⬆️
src/hyperion/parameters/constants.py	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[d-perl]

This is great! I just have one minor comment I think would make it more readable - feel free to do it or not - otherwise looks good to me.

[d-perl]

Nit: I would like it if these names reflected the plans more closely - e.g. ISPYB_PREPLAN_READ and ISPYB_MIDPLAN_READ or something like that, to show that the two are related