Migrate to ophyd-async v0.15 (breaking changes for user-defined devices)

[Tom-Willemsen]

Description of work

Migrates to ophyd-async v0.15.

See https://github.com/bluesky/ophyd-async/releases/tag/v0.15 for details of a breaking change in ophyd-async; the wait= argument has been removed from epics_signal_rw.set(), and instead needs to be specified when setting up the epics_signal_rw.

This is only relevant to users for device classes defined in the instrument scripts area; devices provided directly by ophyd_async or ibex_bluesky_core have been adjusted in this PR or upstream.

Ticket

None.

Acceptance criteria

• Pull request title is understandable for a user (e.g. scientist) reading the release notes. The PR title should be a short description of the change from a user perspective.
• Pull request has appropriate labels for automatic release-notes generation

Documentation

Not applicable.

[FreddieAkeroyd]

This is only relevant to users for device classes defined in the instrument scripts area do we need to mention something in our doc/ ibex release notes? It's not something we have changed, but we do up the ophyd_async version and hence something might break for somebody, or if they are developing at that level they should already know how to manage this?

[Tom-Willemsen]

Our ibex_bluesky_core release notes get auto-generated from PR titles and labels on the PRs - I'd expect any bluesky users to be reading these.

[FreddieAkeroyd]

Ok thanks so that is all covered then.