Read beamline parameters through config server

[jacob720]

Fixes #1504

Link to dodal PR (if required): DiamondLightSource/dodal#1773
(remember to update pyproject.toml with the dodal commit tag if you need it for tests to pass!)

Instructions to reviewer on how to test:

1. Check config is read through config server

Checks for reviewer

• Would the PR title make sense to a user on a set of release notes

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.87%. Comparing base (ac02784) to head (095a052).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1511      +/-   ##
==========================================
+ Coverage   92.86%   92.87%   +0.01%     
==========================================
  Files         153      153              
  Lines        8645     8646       +1     
==========================================
+ Hits         8028     8030       +2     
+ Misses        617      616       -1     

Components	Coverage Δ
i24 SSX	78.60% <ø> (ø)
hyperion	98.22% <100.00%> (+<0.01%)	⬆️
other	98.35% <100.00%> (+0.02%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[DominicOram]

Thanks, looks good.

Could: It feels like there's some general tidying up we can do here, but maybe that would be easier after the other moves to using the config server. For example:

• Why do we have a separate MX config server client that we use sometimes?
• The way we patch "dodal.common.beamlines.beamline_parameters.BEAMLINE_PARAMETER_PATHS", in mx-bluesky is quite odd in that we use i03 for everything and we just patch it all the time rather than patching what we need when we need it

[DominicOram]

Should: Can we not combine this and _fake_config_server_read?

[jacob720]

We have an MX config client which directly reads the the filesystem if the server is down. I think this is no longer viable since the server now does conversions, so we'd have to build that same functionality into the MX config client. Discussed with @olliesilvester a few times and we came to the conclusion we'd delete this, particularly as i03 are happy to use the config server for Hyperion now it's deployed on their beamline cluster.

I think you're right though, it would be easier to do this and other tidying once all the config server PRs are in.