Added I23ZoomController to account for the differing PV names

[adaudon]

Other mx-beamlines use a different PV name for zoom. Created a ZoomController specific to I23.

Fixes DiamondLightSource/mx-bluesky#1771

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 99.15%. Comparing base (641e0a4) to head (d8a2ed9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2097   +/-   ##
=======================================
  Coverage   99.15%   99.15%           
=======================================
  Files         345      345           
  Lines       13472    13482   +10     
=======================================
+ Hits        13358    13368   +10     
  Misses        114      114           

☔ 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.

[DominicOram]

Thanks, I think that rather than make a new device it might be better to just change the ZoomController so you can specify the suffix for the percentage/level. That's what we've done in other places where they have been different. I would also suggest you ask controls to make an alias for CAM:MP:SELECT -> ZOOM:MP:SELECT, we can then reuse the device with no changes