BUG: Fix logging levels with BF loci.plugins.LociImporter

[bramalingam]

ref: ​https://www.openmicroscopy.org/community/viewtopic.php?f=13&t=7993

The following line,
​https://github.com/openmicroscopy/bioformats/blob/develop/components/bio-formats-plugins/src/loci/plugins/LociImporter.java#L69

is basically not allowing any manipulations to the log levels via a script.

[mlinkert]

​https://github.com/openmicroscopy/bioformats/pull/2272 is related. I have some work on this ongoing in a private repository, with the intention of opening a PR early next week (probably after 2272 is merged now, to avoid conflicts). The idea is to make the logging behave sensibly in all of the following cases:

• no binding-specific configuration file, call to DebugTools?.enableLogging(...) either calling code (e.g. third-party app) or called code but not both
• no binding-specific configuration file, call to DebugTools?.enableLogging(...) in both calling code and called code (e.g. ImageJ case above)
• binding-specific configuration file, call to DebugTools?.enableLogging(...) in called code

which means that (1) the configuration file needs to always take precedence, and (2) I think there needs to be an enableLogging signature that lets the log level persist even if enableLogging("...") is called later on by something else. Changing the behavior of the current enableLogging signature to check 2272's isEnabled method before setting the log level might resolve (1).

[sbesson]

Would an API addition like the following allow to solve (1) and (2)
1- DebugTools?.setLogging(...) would always override the logging level whether set by binding-specific configuration file or DebugTools?
2- DebugTools?.enableLogging(...) would first execute DebugTools?.isEnabled(...) and then conditionally set the log level via DebugTools?.setLogging(...) if the logging has not been initialized

[sbesson]

See ​https://github.com/openmicroscopy/bioformats/pull/2372