Upcoming logging change

[pgunn]

Hello,
The next release will have some changes to how logging is done; this is to make it easier to have caiman play nice to being embedded in other software, by allowing the logging caiman does to be separately controlled from other code. If you don't care about logging, nothing you care about will be affected by this particular change.

The way I'll be doing this will be to consistently use a named logger in the codebase (we do a little bit of this, but it's inconsistent and we use the default logger in most places), so if you're calling into caiman and want to control its logging, you'll grab a handle to the logger named caiman and you can tweak its loglevel (or send some loglevels to files, or anything else you might want to do - see the standard python logging module for a full list of things you can ask for).

The demos (jupyter notebooks and cli demos) will be updated to demonstrate this.

I expect this change to be nondisruptive to function; at worst you might start getting more (or fewer) logging messages than you're expecting until you adjust your code.

If you have any questions, reach out. Issue #1376 covers the scope of the work, and it's due to a question in issue #1374