Add EoL and use SetConsoleSinkLevel

[caguero]

This patch:

1. Adds newlines to the logging messages used in the log example.
2. Uses SetConsoleSinkLevel() to only change the verbosity level of the console.

This is the result we should see in the console:

(2024-09-22 20:41:34.090) [info] [:] info
(2024-09-22 20:41:34.090) [warning] [:] warn
(2024-09-22 20:41:34.090) [error] [:] error
(2024-09-22 20:41:34.090) [critical] [:] critical

And this is the result we should see in /tmp/my_log.txt:

(2024-09-22 20:41:34.090) [trace] [:] trace
(2024-09-22 20:41:34.090) [info] [:] info
(2024-09-22 20:41:34.090) [warning] [:] warn
(2024-09-22 20:41:34.090) [error] [:] error
(2024-09-22 20:41:34.090) [critical] [:] critical

If we change the verbosity level using the original call logger.RawLogger().set_level(spdlog::level::trace); the result is confusing because the console only shows:

(2024-09-22 20:44:34.801) [error] [:] error
(2024-09-22 20:44:34.801) [critical] [:] critical

The reason for this is because we have a logger level set to trace and the console sink levels set to err in Logger.cc. spdlog seems to choose the verbosity with higher priority between sinks and logger.

Summary

Checklist

• Signed all commits for DCO
• Added tests
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.