Cxbx-reloaded: Avoid kernel logfile overwriting

[PatrickvL]

Currently, if kernel logging is enabled, Cxbx-Reloaded overwrites the configured log file with the output of each new Xbe that's being launched. This is especially frustrating when multi-xbe titles are being used, or when the dashboard is launched (as contents of prior runs are lost).

For this issue:

• devise one or more solutions for this problem
• discuss the pro's and con's of each suggestion before implementing it
• reach consensus
• implement
• deliver

A quick overview of possible solutions:

• put a logfile next to each Xbe that's being emulated (pro : avoids most overwriting, con : pollutes title folders)
• ask the user to what file must be logged (pro : user becomes responsible, con : cumbersome to use)
• use a naming convention that prevents overwrites (pro : avoids most overwriting, con : logfiles pile up)
  ... etc

[gandalfthewhite19890404]

Some suggestions:

1. Make one log file for one session. Session started as Start emulation button is pressed. Session ended by error(crash) or stopping emulation (by user or shutdown command from dash for example).
2. Naming log file - Title, ID or other unique. Also it may consist timestamp (additionally).
   After loading xbe to emulator it takes game title and ID from xbe, timestamp and create log for session. After this all debug output will write sequently to this session log file without creating separate files - one session logs in one file.

[RadWolfie]

This ticket is outdated since pull request https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/pull/1395 introduced new feature to append to active log file than overwrite it.

[PatrickvL]

The fact logging is now appended covers only part of this issue. It doesn't cover (optional) creation of separate log files for separate xbe's.