Rolling log files in verbose mode

[hubertp]

Motivation

Attempts to reproduce many of the reported bugs typically come down to one question - do we have the logs? So far regular logs are not so helpful because we need them in very verbose mode to observe the exchanges between IDE and the engine.
This is problematic because we have to ask users to either run in verbose mode constantly (can slow down the performance) or kill the current session and try to reproduce the problem with verbose logs (and likely fail).

Proposed solution

Currently, we always log files to enso log file folder. But logs in trace level are very verbose and therefore not turned on by default.
The proposition is to use rolling log files.

[hubertp]

It seems like we have our own implementation of log writer in https://github.com/enso-org/enso/blob/develop/lib/scala/logging-service/src/main/scala/org/enso/loggingservice/printers/FileOutputPrinter.scala.
That's a bit unfortunate since I was hoping that I would be able to just use something that is already present.

GitHub

enso/FileOutputPrinter.scala at develop · enso-org/enso

Hybrid visual and textual functional programming. Contribute to enso-org/enso development by creating an account on GitHub.

[hubertp]

This is done with the work on #7253