Configure logging

[Tom-Willemsen]

Read:

• https://blueskyproject.io/bluesky/main/debugging.html
• https://docs.python.org/3/howto/logging.html#

And then:

• Configure python loggers for ibex_bluesky_core following best practices in the documents linked above
• Add some initial debug logging in "obvious places" e.g. in DAE and blocks devices, ISIS-specific callbacks, describing what they're doing.

We need to do this so that we can get appropriate debugging information to support this system when it's in use on the instruments.

Acceptance criteria:

• ibex_bluesky_core can use python's stdlib logging module to log stuff
• The log messages from both bluesky itself and ibex_bluesky_core, at a suitable log level, end up in c:\instrument\var\logs\bluesky\
• Ensure log file gets rotated every day so that log rotation scripts can move it
• Documentation about how to increase the log level(s) if we need more information to diagnose a problem
• Above location added to log rotation script

[Chsudeepta]

The following PRs have been created:
Changes for logger: #40
Changes for log archiving script: https://github.com/ISISComputingGroup/EPICS/pull/371
Changes for system tests: ISISComputingGroup/system_tests#114

One caveat is that many system tests were failing, including the new ones added here. But these tests ran fine from in isolation (executed as unit tests).

[Tom-Willemsen]

Can we write a follow-up issue for the second acceptance criteria:

Add some initial debug logging in "obvious places" e.g. in DAE and blocks devices, ISIS-specific callbacks, describing what they're doing.

Since it doesn't seem to be in the PRs above?