[CLI] Make per-run log files unique by appending timestamp + open with mode="w" (fixes #984)

[abhisheksingh-esp]

Fixes #984.

Root cause: configure_logger_for_run in
certification-tool-cli/th_cli/test_run/logging.py derived the log file path
solely from --title (test_run_{title}.log) and loguru.logger.add(...)
defaults to append mode. Reusing -n NAME across runs caused successive runs
to be concatenated into the same file.
Change:

• Append a timestamp suffix (_YYYY-MM-DD-HH-MM-SS) to the log filename inside
  configure_logger_for_run, so every run produces a unique file regardless
  of the -n NAME value (matches the convention suggested by @OlivierGre).
• Pass mode="w" to logger.add(...) as defense-in-depth, in case two runs
  ever land on the exact same path (e.g. same second).
  No public API change; configure_logger_for_run(title) still returns the
  resolved path used by run_tests at the end of execution.
  Verification:
• Run the same test twice with -n my_run. Two distinct files in run_logs/,
  each containing only its own run.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Abhishek Singh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[gemini-code-assist]

Code Review

This pull request updates the logging configuration to include a timestamp in log filenames and sets the file mode to write. A review comment identifies a potential portability issue on Windows systems where the 'title' parameter might contain invalid characters like colons, and provides a code suggestion to sanitize the string.

[antonio-amjr]

Hi @abhisheksingh-esp,

Seems good, but I would like to ask for a little change if I may.
Let me know what you think of the suggestion below.

[antonio-amjr]

Can we use the .isoformat() for the timestamp?
It will have the appropriate format (YYYY-MM-DDTHH:MM:SS.ffffff) and we would use a standard approach.

Suggested change

	timestamp = datetime.datetime.now().strftime(_LOG_TIMESTAMP_FORMAT)
	timestamp = datetime.datetime.now().isoformat()

Let me know what you think and if that works.

[abhisheksingh-esp]

Agreed — using .isoformat() makes sense here. It already provides the correct standardized format (YYYY-MM-DDTHH:MM:SS.ffffff) and keeps the implementation cleaner and more consistent.

Only one catch: isoformat() produces timestamps containing :, which makes the filename invalid on Windows (and some network/USB filesystems). This could create issues if the log file is copied to or opened on a Windows machine.

[antonio-amjr]

Good catch about Windows systems.

Maybe that's not the best option.
Or maybe we could replace all : for - from the isoformat's output.

In that case, please feel free to continue with your solution if that would be a pain in Windows machines. Since my team is not using, sometimes those details may slip.

[antonio-amjr]

Let me know which approach do you think would be better for all systems in this case