There was only a global preprocessor guard that globally includes or removes all code from Log statements.

Once there are a combination of library and application Log modules and statements, it becomes desirable to disable those Log statements and their inclusion in code at a more granular level than globally.

This features adds an additional requirement that a Log module-level define for a Log statement be included in compiled code.

`ti_log_Log_ENABLE_<MyLogModuleName>=1` must be set for a Log statement to be emitted by the preprocessor during compilation. Anything else will cause the Log statement not to be emitted during compilation.

When using SysConfig, `ti_log_Log_ENABLE_<MyLogModuleName>=1`  is automatically emitted into `ti_utils_build_compiler.opt` whenever `<MyLogModuleName>` is enabled as a LogModule instance in SysConfig.