Use daq config server for UndulatorDCM config

[jacob720]

Fixes #1494

Link to dodal PR (if required): DiamondLightSource/dodal#1768
Also requires https://gitlab.diamond.ac.uk/MX-GDA/hyperion-system-testing/-/merge_requests/7
Reads UndulatorDCM config through the config server.

Also adds system tests and changes existing system tests to use a locally deployed real config server rather than mocking the client as is done in unit tests.

Instructions to reviewer on how to test:

1. Check tests pass
2. Check system tests pass

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 (7b58d00) to head (cbec4e9).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1497      +/-   ##
==========================================
- Coverage   92.88%   92.87%   -0.01%     
==========================================
  Files         155      155              
  Lines        8498     8492       -6     
==========================================
- Hits         7893     7887       -6     
  Misses        605      605              

Components	Coverage Δ
i24 SSX	77.32% <ø> (ø)
hyperion	98.59% <100.00%> (-0.01%)	⬇️
other	98.30% <100.00%> (-0.01%)	⬇️

🚀 New features to boost your workflow:

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

[rtuck99]

Looks fine to me, however would be nice to see some minimal system tests with the config server so that we can verify we can read configs. I think also that having such tests also does help with thinking about endpoint configuration.

[rtuck99]

could consider renaming the file here to config_client

[rtuck99]

I think echoing what other people have said elsewhere, we should be able to locate the config client without having to specify the beamline. At a device level we could inject the config client via a fixture with the correct endpoint and not need to know the specific beamline or have get_config_client(), at least in devices experiment plans, we may need something to retrieve the correct client in a plan occasionally, but the plan shouldn't need to know which beamline it's on, only the type of resource it needs.

[rtuck99]

Approved, just need changes in the dodal PR as discussed