Update logging mechanism to make use of Serilog

[AdmiringWorm]

Detailed Description

Update GRM to make use of Serilog for logging purposes (both to file and to console).

Currently the logging mechanism uses custom logic to log text to a file, and normal Console calls to output to the console. However this should be changed to use Serilog instead.

Context

Quoting Gary:

add a proper logger into GRM, so we get a bit more control over the text that is written to the output

Possible Implementation

Already mentioned.

Your Environment

Not Important

[Cheesebaron]

I think we should consider using Microsoft.Extensions.Logging and then hook that up with Serilog in the "client", rather than taking a hard dependency on Serilog.

This will make it easy to switch to another Logging framework in the future if needed.

[AdmiringWorm]

That could certainly be done as well.

@gep13 thoughts?

EDIT: This would require us to implement some kind of DI though.

[gep13]

I have no objections to bringing that in.

I had thought about bringing in DI as well, since it would make the different providers easier to use.

[AdmiringWorm]

@gep13 Sounds like more refactoring need to be done then.

Most likely we'll need to refactor the code base to have a single class we call for each command (which then again calls out to the correct provider).

I opened a draft with the implementation of Serilog, but without DI for now.
Not completely done yet, but getting there.

[arturcic]

for the DI I would suggest Microsoft.Extensions.DependencyInjection, we used it for GitVersion

[AdmiringWorm]

Created #181 for discussing and tracking implementation of a DI framework