autoscript performance enhancement: provide method to check current logging level

The service object now sports log_debug() and log_info() methods. Maximo autoscripters are thankful for the option to choose the level we log messages at. The next step is to allow us to optimize performance by allowing us to choose when we try to log messages.

If we call service.log_debug("some context {}".format(mbo.getString("SOMEATTR"))), then the string formatting work will be done and the resulting string will be sent to log_debug(). There is currently no way to easily and accurately confirm that the string sent to log_debug() will, in fact, make it into the logs. The log_debug() call may just discard that string we went to the trouble of assembling.

Please provide an easy and accurate way to avoid the performance hit of doing string work if the resulting string is just going to be discarded by the log_debug() or log_info() call.

IBM is obviously free to design a solution as they please. However, I offer the following suggestions.

1. Enhance the service object / ScriptService class to have a getLogger() method. The method would take no arguments and return the MXLogger where service.log_debug() messages would go. This would allow developers full, direct access to the script's logger without having to guess / assume it is "maximo.script.SCRIPTNAME". Developers can then then call that logger's isDebugEnabled(), or etc, as needed. This seems to me to be the least effort for IBM and also the biggest win for developers.

2. Enhance the service object / ScriptService class to have log_debugEnabled() and etc methods. Then developers can call make calls to log_debug() and etc conditional to whether that level is enabled.