Update to ophyd-async 0.6.0

[DiamondJoseph]

Fixes #794

Instructions to reviewer on how to test:

1. Do thing x
2. Confirm thing y happens

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 94.91%. Comparing base (cc5ccf1) to head (157720a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #796   +/-   ##
=======================================
  Coverage   94.90%   94.91%           
=======================================
  Files         115      115           
  Lines        4675     4677    +2     
=======================================
+ Hits         4437     4439    +2     
  Misses        238      238           

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

[DominicOram]

One comment, otherwise looks good.

[DominicOram]

Given the tests are on 3.10 only and mention timeouts I'm going to bet that they're to do with TimeoutError and asyncio.TimeoutError being different in 3.10. Probably caused by bluesky/ophyd-async#573

[DiamondJoseph]

TimeoutError and asyncio.TimeoutError being different in 3.10. Probably caused by bluesky/ophyd-async#573

For now I've imported TimeoutError from asyncio: in 3.10 this will be the asyncio.TimeoutError, in >3.10 this returns the builting TimeoutError. Either TypeChecking will shout at us or there's this ticket to remove the import after 3.10

Changes addressed