Change type of robot error code PV

[DominicOram]

Part of DiamondLightSource/hyperion#1465

Instructions to reviewer on how to test:

1. Run dodal connect i03
2. Confirm robot is now happy

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}

[olliesilvester]

Looks good, but I've noticed we have a few other places where we create epics signals with type int:

in fast_grid_scan smargon, tetramm, epics_util, xspress3, xspress3_channel

If we'd get a same issue for all of these, maybe we should change the rest of the devices too?

[DominicOram]

Looks good, but I've noticed we have a few other places where we create epics signals with type int:

in fast_grid_scan smargon, tetramm, epics_util, xspress3, xspress3_channel

If we'd get a same issue for all of these, maybe we should change the rest of the devices too?

For most of these they're not an ao record in EPICS, they're either longs or binary. You could argue that we shouldn't be using ints at all for the binary ones I guess but the longs are fine. Basically, if the device connects then it's fine. All these devices connect when we do dodal connect i03 except the tetramm, which seems fine when I do dodal connect i22.