Remove MXConfigClient #1629
Description
The main reasons for the MXConfigClient were to include feature settings, and to directly read the filesystem if we didn't get a response from the server. With the introduction of config models to the config server, and the ability to deploy the seer to beamline clusters if needed, these issues have been solved, so we should remove the MXConfigClient.
This will involve creating pydantic models in the daq-config-server repo for any feature settings and requesting them from the config server in mx-bluesky. These models will look very similar to I04FeatureSettings and HyperionFeatureSettings currently in mx-bluesky.
This will probably also mean we can delete get_i04_config_client() and get_hyperion_config_client().
Acceptance Criteria
- Pydantic models are created for feature settings
- These are read from the config server
- MXConfigClient and associated code is removed