Update bluesky and pin pyright

[DominicOram]

Fixes #1041

Instructions to reviewer on how to test:

1. Run unit tests and confirm they still pass
2. Confirm new type hints look correct
3. Confirm no new typing errors

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 97.69%. Comparing base (5893821) to head (e7d1dbd).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1072   +/-   ##
=======================================
  Coverage   97.69%   97.69%           
=======================================
  Files         160      160           
  Lines        6635     6638    +3     
=======================================
+ Hits         6482     6485    +3     
  Misses        153      153           

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

[DominicOram]

Latest pyright is also more fussy, I will pin that in this PR too and improve in #1079

[olliesilvester]

Thanks! Question about the wrapped functions but we can put that in a separate issue

[olliesilvester]

This can be another issue, but maybe we can remove a bunch of these now that typing has improved? @DiamondJoseph are these wrappers still useful?

[DiamondJoseph]

Oooh the bluesky type hinting went in

[DiamondJoseph]

These wrapped stubs are still required for blueapi because the bluesky version plan stubs aren't serializable.

[DominicOram]

So they are going to be needed permanently? Can we make the comment clearer then? Currently it reads:

"""
Wrappers for Bluesky built-in plan stubs with type hinting
"""

Which is confusing given we already have types here