Update profiling CLI arguments

[4e6]

Pull Request Description

PR adds/updates CLI flags:

• --profiling-events-log-path <file> enable the event logging with ability to specify the file to store the messages between the runtime and the language server
• --profiling-path <file> enable the application profiling with ability to specify the file to store the .npss sampling statistics
• --profiling-time <seconds> limits the application profiling time. If not specified, the profiling is stopped on the application shutdown

Important Notes

Checklist

Please include the following checklist in your PR:

• The documentation has been updated if necessary.
• All code conforms to the Scala, Java, and Rust style guides.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed: Enso GUI was tested when built using BOTH ./run dist and ./run watch.

[JaroslavTulach]

One more request. The IDE logs events it sends to the language server engine runtime. Can we make sure the same events, with the same IDs and similar timestamps are in the generated .log file? We need this to pair the two logs - having additional events in the log isn't necessary - in fact too many events may complicate orientation on the timeline.

[JaroslavTulach]

Let's get this in and let's see how well it works!

[JaroslavTulach]

Yup, this looks like fine order of actions. Stopping sampling before terminating Truffle.

[4e6]

Can we make sure the same events, with the same IDs and similar timestamps are in the generated .log file?

The logging goes through the central logging service. I updated the logic, and not it also produces the profiling log when the profiling is enabled. This way the log captures all the messages as the previous solution with the Java log handler was only able to capture logs from within the runtime.