Refactor wrapped scan plans so they more user friendly

[oliwenmandiamond]

This change aims to make the scan syntax much more user friendly. Some examples are show below:

Old syntax

from dodal.plans import wrapped as dpw
>>> RE(dpw.list_grid_scan([], [(x, [1, 5, 10, 50]), (y, [2, 5, 10, 15, 18])]))

>>> RE(dpw.step_grid_scan([], [(x, [1, 10, 1]), (y, [1, 5, 1])]))

# Blueapi client example
>>> bc.plans.step_grid_scan([], [(x, [1, 10, 1]), (y, [1, 5, 1])])

New syntax

>>> RE(dpw.list_grid_scan([], [x, [1, 5, 10, 50], y, [2, 5, 10, 15, 18]]))

>>> RE(dpw.step_grid_scan([], [x, 1, 10, 1, y, 1, 5, 1]))

# Blueapi client example
>>> bc.plans.step_grid_scan([], [x, 1, 10, 1, y, 1, 5, 1])

When BlueAPI supports *args, we can simplifier this even further by removing the final set of brackets:

>>> RE(dpw.step_grid_scan([], x, 1, 10, 1, y, 1, 5, 1))

or BlueAPI client equivalent

>>> bc.plans.step_grid_scan([], x, 1, 10, 1, y, 1, 5, 1)

I've also tried to improve the tests, they now check that the scan shape is correct and checks every custom error message for scan syntax being wrong for step scans.

Instructions to reviewer on how to test:

1. Check implementation and logic is correct
2. Test coverage is sufficient.

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 99.33%. Comparing base (a554a5d) to head (425e708).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2050      +/-   ##
==========================================
+ Coverage   99.19%   99.33%   +0.14%     
==========================================
  Files         367      367              
  Lines       14598    14367     -231     
==========================================
- Hits        14481    14272     -209     
+ Misses        117       95      -22     

☔ View full report in Codecov by Harness.
📢 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.

[EmsArnold]

A few comments, but hopefully nothing too onerous. I would like to try it on test rig or similar if it hasn't been tested there yet.

[EmsArnold]

Should: have an updated description

description="Sequence of Movable, float, or int. For independent \
trajectories, provide '[movable 1, start1, stop1, num1, movable2, \
start2, stop2, num2, ..., movableN, startN, stopN, numN]'."

[EmsArnold]

Should: have an updated description

description="Sequence of Movable, float, or int. ...

[EmsArnold]

Should: have an updated description

description="Sequence of Movable, float, or int. For independent \
trajectories, provide '[movable 1, start1, stop1, num1, movable2, \
start2, stop2, num2, ..., movableN, startN, stopN, numN]'."

[EmsArnold]

Is there a reason for this remain a list rather than a Sequence, as the others have been swapped?

[EmsArnold]

Should: have an updated description

description="Sequence of Movable or list containing float or int. For concurrent \
trajectories, provide '[movable 1, [point1, point2, ...], movable2, [point1, point2, ...], \
..., movableN, [point1, point2, ...]]'. Number of points for each movable must be equal."