docs: add a security notice to the use of CI_DEBUG_TRACE

So you may simply manually run your pipeline, and set `TRACE=true` interactively.

:warning: this is different (and complementary) to GitLab's [`CI_DEBUG_TRACE`](https://docs.gitlab.com/ee/ci/variables/#enable-debug-logging) variable.

This is different (and complementary) to GitLab's [`CI_DEBUG_TRACE`](https://docs.gitlab.com/ee/ci/variables/#enable-debug-logging) variable.

!!! warning "Security notice"

    When using the `CI_DEBUG_TRACE` variable in GitLab, it's important to be aware of the potential security risks associated with it. 

    Setting `CI_DEBUG_TRACE` to `true` enables detailed tracing of all commands executed during a CI/CD job, including the output of 

    environment variables, command arguments, and any sensitive information that might be exposed during the pipeline's execution. 

    This can include credentials, tokens, API keys, and other confidential data. 

    If these logs are not properly secured, they can be accessed by unauthorized users, leading to potential security breaches. 

    Therefore, it is recommended to use `CI_DEBUG_TRACE` only when necessary and to ensure that sensitive information is appropriately 

    masked or removed from the logs. 

    Additionally, access to these logs should be restricted to authorized personnel only to minimize the risk of exposing critical information.

## Docker Images Versions