I19 optics: pass an instrument session to the optics hutch devices

[noemifrisina]

See blueapi#1187

As of blueapi 1.0.0 the instrument_session is a required field in the REST call for posting a plan. We don't yet have a way for propagating it to the optics hutch devices (see linked ticket), but for the moment it should be enough to pass the latest commissioning directory.

Instructions to reviewer on how to test:

1. Run tests

Checks for reviewer

• Would the PR title make sense to a scientist on a set of release notes
• If a new device has been added does it follow the standards
• If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
• Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.75%. Comparing base (411f853) to head (54fd745).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1493   +/-   ##
=======================================
  Coverage   98.75%   98.75%           
=======================================
  Files         235      235           
  Lines        8641     8642    +1     
=======================================
+ Hits         8533     8534    +1     
  Misses        108      108           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[olliesilvester]

Can you link to DiamondLightSource/blueapi#1187 in comments here?

[noemifrisina]

Good point, yes