Add more drop-in places

[mrakitin]

There should be a way to have the following drop-in places:

• shell:
  • before the main test (already have it, called .ci/bl-specific.sh)
  • after the main test, to be able to run caget, caput, etc.
• Python:
  • run custom code before running the startup Python files, but after the caproto IOC has started
  • run custom code after running the startup Python files (already exists, called .ci/drop-in.py). It won't be executed in case the prior files loading failed.

We need to define consistent/clear names for those files.

Prompted by NSLS-II-OPLS/profile_collection#10 (comment).

[mrakitin]

@jklynch, what would be your suggestions for the names? I am thinking about the following:

• .ci/pre-test.sh (a new name of .ci/bl-specific.sh)
• .ci/post-test.sh
• .ci/pre-test.py
• .ci/post-test.py (a new name of .ci/drop-in.py)

Should we differentiate the .py files more (e.g., different name, or use underscores, or something else), so that the files are not confused. Maybe a prefix such as shell-pre-test.sh and python-pre-test.py? Too repeating?

[jklynch]

pre-test.sh and post-test.sh seem pretty good. Nothing else springs to mind for me.

Would pre-startup.py and post-startup.py make sense for the python scripts? Or pre-ipython-startup.py and post-ipython-startup.py? The second ones are pretty long but descriptive.