partially close: #2847

Logging debug messages can lead to significant memory allocations,
especially when outputting variable values. In Go, even if log_level is
not set to debug, these allocations can still occur because the program
evaluates the debug statements regardless of the log level.

To prevent unnecessary memory usage, you can strip out all debug-level
code from the binary at compile time using build flags. This approach
improves the performance of CometBFT by excluding debug messages
entirely, even when `log_level` is set to `debug`. This technique is
ideal for production environments that prioritize performance
optimization over debug logging.

> Note: Compiling CometBFT with this method will completely disable all
debug messages. If you require debug output, avoid compiling the binary
with these settings.

In order to build a binary stripping all debug log messages (e.g.
`log.Debug()`) from the binary, use the `nodebug` tag:
```
COMETBFT_BUILD_OPTIONS=nodebug make install
```

once it's installed you can run a `kvstore` example with `log_level =
"debug"` set in the `config.toml` and you will see that no debug
messages are shown in the log.

cc: @ValarDragon

#### PR checklist

- [ ] ~~Tests written/updated~~
- [X] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [X] Updated relevant documentation (`docs/` or `spec/`) and code
comments

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit 51e9948)