Fixes #113
Fixes #94
Fixes #95

This PR would allow solving #94 and #95 with the following call, although disabling logs is not the direct purpose of this PR:

_mongoRunner = MongoDbRunner.Start(logger: NullLogger.Instance);

How it works

When starting the mongod process, the ProcessControl evaluates if an ILogger has been injected or if it's null. If null, then MongoRunner works as usual, by wiring the logs to .NET's console and debug outputs. Otherwise, it parses mongo's logs and wires them to the ILogger.

Parsing mongo's logs is a discussable choice. I'm open for discussing this choice. I mainly needed to parse the json logs to get the severity so that we would call ILogger with the appropriate level.

Risks and Impacts

• Added 2 new dependencies: Microsoft.Extensions.Logging.Abstractions for the ILogger interface, and System.Text.Json to parse the mongo logs.
• Parsing the mongo logs totally depends on Mongo's definition of their logging structure. If they decide to break the format, we'll have to adapt. Notice an error in their documentation: they reported the id property to be a string, whereas it is actually an int.
• This is slightly unrelated. I removed the argument string windowTitle from the ProcessControl.StartAndWait() methods, as I noticed they were unused. However, the class and the methods are public, meaning it could break usage if anyone has been using these methods. I believe the class ProcessControl should remain internal. Is that correct? Do we risk breaking anyone's usage with the changes I made here?

Performance

I ran this modified version of Mongo2Go on a test suite of 296 passing tests. I have not noticed any significant impact or improvement on execution time of the test suite. Duration kept between 02:00 and 2:20 (parallel), or 20-25 minutes cumulative. No significant change either caused by the logging level or the logging target.