[LCLSECSD-346] pcds-envs (pcds_conda) can interfere with engineering_tools settings (libca / caget / etc)

Expected Behavior

• engineering tools scripts should not be dependent on the shell environment
  • i.e., the scripts should be standalone and setup environment settings as needed

Current Behavior

• Some scripts do not work when pcds_conda is activated

For example, using env -i ... to ignore my bashrc/bash_profile entirely, the following works without issue:

$ env -i bash --noprofile --norc
bash-4.2$ export PATH=/reg/g/pcds/engineering_tools/latest/scripts:$PATH
bash-4.2$ motor-expert-screen MY:MOTOR
bash-4.2$ exit

$ env -i bash --noprofile --norc
bash-4.2$ source /cds/group/pcds/pyps/conda/pcds_conda
(pcds-5.1.1) bash-4.2$ export PATH=/reg/g/pcds/engineering_tools/latest/scripts:$PATH
(pcds-5.1.1) bash-4.2$ motor-expert-screen MY:MOTOR
caget: error while loading shared libraries: libreadline.so.5: cannot open shared object file: No such file or directory

Possible Solution

Steps to Reproduce (for bugs)

See above.

Context

Failing to use engineering tools scripts with pcds_envs activated

Your Environment

Can be a clean environment - see examples above.

Start by reproducing the failure with the motor-expert-screen entry point in a clean shell, both with and without /cds/group/pcds/pyps/conda/pcds_conda sourced. Trace how the scripts invoke caget and load libreadline.so.5; done means the engineering tools scripts work with pcds_conda activated without relying on the caller's shell environment.