Allow for all scan directions in the OAV parameters

[noemifrisina]

Temporarily reverts #2092 and changes the OAVParameters direction in order to allow values different from 0 and 1 from the OAVCentring file, eg. I19-1 has a direction value of "2", which is "up".

This issues should be fixed properly in a separate PR.

Instructions to reviewer on how to test:

1. Run tests

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.16%. Comparing base (4463efb) to head (40e856c).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2138      +/-   ##
==========================================
- Coverage   99.16%   99.16%   -0.01%     
==========================================
  Files         354      354              
  Lines       13832    13831       -1     
==========================================
- Hits        13716    13715       -1     
  Misses        116      116              

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

[rtuck99]

Approved