Switched from caproto to pyepics

[jklynch]

During the 2021-1.0 deployment we had to switch from caproto to pyepics to deal with this problem:

File "/opt/conda_envs/collection-2021-1.0/lib/python3.7/site-packages/bluesky/run_engine.py", line 1683, in _read
    await current_run.read(msg, ret)
  File "/opt/conda_envs/collection-2021-1.0/lib/python3.7/site-packages/bluesky/bundlers.py", line 176, in read
    self._config_desc_cache[obj] = obj.describe_configuration()
  File "/opt/conda_envs/collection-2021-1.0/lib/python3.7/site-packages/ophyd/device.py", line 1276, in describe_configuration
    res.update(component.describe_configuration())
  File "/opt/conda_envs/collection-2021-1.0/lib/python3.7/site-packages/ophyd/signal.py", line 434, in describe_configuration
    return self.describe()
  File "/opt/conda_envs/collection-2021-1.0/lib/python3.7/site-packages/ophyd/signal.py", line 1248, in describe
    dtype=data_type(val),
  File "/opt/conda_envs/collection-2021-1.0/lib/python3.7/site-packages/ophyd/utils/epics_pvs.py", line 323, in data_type
    f'Cannot determine the appropriate bluesky-friendly data type for '
ValueError: Cannot determine the appropriate bluesky-friendly data type for value b'mm' of Python type <class 'bytes'>. Supported t$

Using caproto was a historical choice made when running on a windows computer but now RSOXS is using linux, so this brings RSOXS into line with most other beamlines.