Custom logging override still produces default log file

[SimonCropp]

When a user overrides logging to use a custom one, the host override is too late and the default log still executes creating a default log file with at least 2 INFO entries in it.

This occurs because INFO is the default level.

A solution is to ensure all logging entries before the user can override are below the default INFO level.

Raised by @johnsimons
Migrated from by Particular/NServiceBus#2574

[SimonCropp]

what happens if an error occurs before we get to the users custom override?
Raised by @SimonCropp

[SimonCropp]

We back to square one 😞
Raised by @johnsimons

[SimonCropp]

How about we add a magic appSettings key that allows the user to specify a type that will be called as early as possible by our host to setup logging ?
Raised by @johnsimons

[johnsimons]

@SimonCropp v6 of the host is ready to go out, should we wait for this fix too?

[SimonCropp]

@johnsimons i dont have an opinion

[SimonCropp]

@johnsimons so how was "an error occurring before we got to the users custom logging" handled in v4?

[johnsimons]

no idea @SimonCropp

[johnsimons]

Fixed in 3778f7d