Preparatory work for Hyperion supervisor: Hyperion planrunner refactor

[rtuck99]

Preparatory work for

• Hyperion blueapi supervisor service #1365

Requires:

• Ability to launch blueapi and run Hyperion plans #1389
• Fixes to support hyperion-blueapi dodal#1760

This updates the PlanRunner to make the move_to_udc_default_state and clean_up_udc plans something that is invoked using the same mechanism as the main load_centre_collect_full plan.

PlanRunner is further subclasses into an InProcessRunner in anticipation of implementing a sibling class which implements plan execution using a BlueAPI client to a remote server.

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 user on a set of release notes

[codecov]

Codecov Report

❌ Patch coverage is 98.54015% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.29%. Comparing base (58f0ca1) to head (5b392ce).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1531      +/-   ##
==========================================
+ Coverage   92.28%   92.29%   +0.01%     
==========================================
  Files         143      144       +1     
  Lines        8126     8167      +41     
==========================================
+ Hits         7499     7538      +39     
- Misses        627      629       +2     

Components	Coverage Δ
i24 SSX	78.56% <ø> (ø)
hyperion	97.90% <98.51%> (-0.05%)	⬇️
other	98.00% <100.00%> (+<0.01%)	⬆️

🚀 New features to boost your workflow:

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

[jacob720]

Looks good to me

[jacob720]

Does the version need bumping with these changes?

[rtuck99]

Strictly speaking, I guess since the changes are additions to the interface rather than changes to existing it would be a micro-version increment.

TBH I think the parameter versioning is not terribly important at the moment. We don't persist these parameter models anywhere and so far the only users are GDA, the as-yet non-existent hyperion-supervisor, and the external callbacks (via bluesky events). These all get corresponding changes whenever the parameter models are changed. So the chance of client and servers interacting with a different version of the parameter model is pretty minimal.

PARAMETER_VERSION doesn't appear to have changed for almost exactly a year, and I'm sure we've made other changes since then so I think it is kind of just stuck on 5.3.0 for the time being until there is a need to change it.