Include robot version info in log.html and report.html

[9nehS]

Background

We are using robotframework to execute our E2E test cases for automotive industry. And we are keeping updated with the latest robotframework releases. Sometimes when we open the report.html or log.html, there is no way for us to find out which robot version we are using (Correct me if I am wrong).

Suggestion

When we open log.html or report.html, we can see which robot version was used to generate those logs and report. Maybe from the upper right or lower right of the html files.
Example: Robot version: Robot 7.0.1 (Python 3.11.2 on win32)

[sylvesterboris]

I’ve added a small but useful enhancement to the HTML reports by displaying the Robot Framework version directly in the top-right corner of both log.html and report.html. Earlier, the version was only available in the HTML metadata, which wasn’t easily visible to users. This change makes the full version string (including Python version and platform) immediately accessible without inspecting the source. The implementation is purely additive and backward-compatible, works seamlessly in both light and dark themes, and gracefully falls back if version data isn’t available. I’ve tested the change by generating sample reports and verified correct visibility, positioning, and styling across themes.

[LucianCrainic]

Bumping this since it's a great QOF feature to have especially when keeping track of all the tests execution.

[pekkaklarck]

I'm not certain is adding the version information so that it is directly visible is a good idea. These are the main reasons:

1. Most users don't seem to need it.
2. It's unclear what information there should be after Rebot execution. I would assume that you'd typically want to see the execution environment info (i.e. robot --version), but PR Add Robot Framework version display to HTML reports #5583 adds information of the tool generating log/report (i.e. rebot --version). Adding the former would require parsing this information from output.xml/json files, but it would then nevertheless be wrong if those output files are regenerated with Rebot. We needed to store execution environment information separately to be able to preserve it.
3. There's also other kind of execution related information that would be useful to see in log and/or report. Most importantly, seeing values of various command line options would be useful. It would be good to design all this in one go.
4. It would be good to be able to control is this information shown or not. Robot/Rebot version most likely isn't critical, but disclosing other information may not always be a good idea.

My preferred approach would be having this information behind a menu, a popup, or something similar. The info could then contain Robot version, Rebot version (if used separately), environment information, command line options, and so on. Designing and implementing this properly is obviously quite a lot work, especially if we start storing some of this information separately in output.xml/json files.

The above said, I'm willing to consider merging #5583 if there's a general consensus that the info is useful and not just noise. This PR only makes UI changes and they can be updated or reverted without backwards compatibility concerns later if needed. Because the information effectively is Rebot version, not Robot version, I just don't think it is generally useful. If you have opinions related to this, please add a comment. I'll also ask opinion from others on the #devel channel on our Slack.