[General] Logging & launching improvements

[CommandMC]

Main changes:

• Logs are now live (meaning new output is written to the file immediately instead of waiting for game exit)
• If an error happens, part of the log is still written (as much info as possible is provided, to help debug the issue)
• Errors themselves are now logged with a stacktrace (not too helpful in production since function & file names are minified, but might help in development)
• The "Error log"/"Game log" (stdout & stderr) split was removed, it's both in "Game log" again now
• The log now contains a timestamp

Other changes:

• getRunnerCallWithoutCredentials is exported again since it's needed for the new log behavior
• Some code cleanup, didn't bother to open a separate PR for just that

---

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[Nocccer]

Have some suggestions and ideas we need to talk about.

[Nocccer]

I left some suggestions. For me it is important to have readable strings in the source code. A string with 1-2 linebreaks is maybe readable and therefore fine, but multine strings should be fast readable, especially with alot of linebreaks.

[Nocccer]

Sorry for this discussion about how to represent multiline strings.
I would say if eslint puts everything in one line, don't use + or join.
If the string is pretty long (longer than the eslint rule) use + or join.
What do you think?

[CommandMC]

What do you think?

I honestly don't really mind. Whatever works works for me, if you want a specific style then I'll use that specific style

[Nocccer]

Sorry for this back adn forth.
I think the best way is to write code always in mind someone else needs to understand it possible with the least effort. So readable code is the key.

But LGTM now.