Add LoggerFactory.Create method

[pakrym]

Adds the LoggerFactory.Create that simplifies LoggerFactory creation in cases where dependency injection is not used in the application.

So the pattern becomes:

var loggerFactory = LoggerFactory.Create(builder => 
    builder.AddEventSourceLogger()
           .AddConsole()
           .AddFilter(...));

Fixes: #615

[davidfowl]

This is slightly unfortunate. But not the end of the world I guess.

[davidfowl]

The fact that we need to hold onto the container means all of the sample code is sorta busted

[pakrym]

Busted how?

[davidfowl]

Maybe you’re saying we don’t need to dispose the service provider?

[davidfowl]

Why does this wrapper exist to begin with?

[pakrym]

To dispose ILoggerProviders created by DI

[davidfowl]

Doesn’t disposing the factory do that?

[davidfowl]

Ah, I see it wouldn’t. That makes the current usage without this API leaky.

[pakrym]

If you don't dispose the service provider - yes.

[davidfowl]

I’m taking about examples that you would use today (even in our samples)

[pakrym]

Pushed a sample fix.

[ryanbrandenburg]

It seems that this change caused these failures in my PR build. It actually showed up in your PR check too, but as a warning instead of an error.

@natemcmaster 1. Is the proper solution here (assuming it is an approved breaking change) to edit this line? 2. Should this kind of change be a warning or an error?

[natemcmaster]

@ryanbrandenburg does your PR invoke build with --warnaserror?

[ryanbrandenburg]

Yes, that's what Arcade defaults to. We can certainly override that anywhere (or everywhere), but I thought I'd ask since this seems like the kind of thing we might want to fail a build (even if it's just so we can document that this was an intended break).