Extract configuration variables into configuration files outside of Bluesky

Move certain values out of I24 python files and into confiugration files instead so they don't constantly need to be committed and are under more control of beamline scientists.

Some examples are:
- cs_maker.json
- pv_abstract.py

## Acceptance Criteria
- Most key/value pairs are extracted into configuration files in daq_configuration unless there's a valid reasoning to keep it inside the repo.

Start by reviewing the I24 Python files, including pv_abstract.py, and the example cs_maker.json configuration. Identify key/value pairs that belong in daq_configuration and check how those files are currently consumed. Done means most configurable values are externalized unless a valid reason keeps them in the repository.

Written by the indexing model from the issue text.