Remove check for zoom levels in ZoomController

[DominicOram]

In the ZoomController we currently raise a ZoomLevelNotFoundError if the zoom levels set by the user do not match the levels specified on the device. These could be different as we use a string signal but the device actually has an enum. The only purpose of this check is to give a nice exception to the user that lists the possible values that the zoom controller has. However, this behavior should probably be in ophyd-async (if it's not already).

Acceptance Criteria

• Test what ophyd-async does if you try and set an enum with in invalid string
• If ophyd-async responds with an error containing the actually valid strings then remove this check in dodal
• If not add this behavior to ophyd-async

[olliesilvester]

Discussed this with @shihab-dls, and we are wondering if it's better to use ophyd-async's StrictEnum for ZoomController.level. To me this would be better since:

• If our enum options don't match the options on the IOC then we will catch that upon device connection
• Easier to develop when we can see the Enum options in code
• It makes more sense for ophyd-async to do the check on valid options for Enum signals than for str signals

[DominicOram]

I think SubsetEnum might be better. In general I prefer SubsetEnum to StrictEnum as if a new option is added to the EPICS side but isn't ever used in DAQ there's no reason for the DAQ code to break.

[olliesilvester]

@shihab-dls found that ophyd-async doesn't error if you set an Enum signal to a random string.
I think this is what we want to do:

• Change ZoomController.level to SubsetEnum instead of a str signal type
• In ophyd-async, add a check so that when an Enum signal is set with a string, we make sure the value is allowed using describe, (using the same logic as we have in ZoomController)