GLAS - SECURE_LOG_LEVEL should enable lightz debug logs

Currently, when setting the SECURE_LOG_LEVEL variable, we receive lightz-aio debug logs only if the analyzer does not time out. This behavior limits our ability to gather useful logs during lengthy scans that may exceed the timeout threshold.

Proposed Changes

We would like to modify this behavior to achieve the following objectives:

1. Real-Time Log Transmission: Modify the way lightz-aio logs are sent to the analyzer so that they are transmitted live. This change would ensure that we receive logs even if the scan reaches the timeout, rather than collecting them only at the end of lightz-aio execution.

2. Include Engine Debug Logs: Add a flag to the analyzer that allows for the inclusion of engine debug logs. This could be implemented within Lightz-AIO by introducing an environment variable that forces lightz-aio to collect and transmit engine logs as well. Specifically, we would set the LIGHTZ_CORE_DEBUG=1 environment variable and include the -debug flag in the command line. It is essential to ensure that these engine debug logs are also transmitted and collected live to effectively manage job timeouts.

3. Update Lightz makefile - remove the note that LIGHTZ_CORE_DEBUG should be set when executing lightz-aio.

By implementing these changes, we aim to enhance our logging capabilities and improve our ability to troubleshoot issues during scans.