[LOG4J2-3404] Creates default layouts using the available Configuration

[ppkarwasz]

When a default PatternLayout is created without a Configuration a new DefaultConfiguration is created and abandoned. This causes a leak of ConsoleManagers.

This PR provides a Configuration argument whenever possible.

[carterkozak]

Change looks good!

I think that new DefaultConfiguration() in PatternLayout.Builder.build() is a bug, perhaps the layout itself should handle a null configuration gracefully? Not necessarily a requirement for this PR as we're ensuring we're passing the correct reference everywhere, but I think the new DefaultConfiguration() that doesn't come from a ConfigurationFactory has high likelihood of causing similar problems again in the future.

[ppkarwasz]

@carterkozak: I'll check if we can leave the Configuration as null and update the PR.

[ppkarwasz]

This requires more explanations: the PatternParser does not use a configuration directly (or has null checks), but allows one to be injected into the PatternConverters.

Looking at the available PatternConverters, the color converters, "enc", "equals*", "highlight", "maxLength", "replace", "style", "ex*" require a configuration to create a PatternParser.

I didn't find any converters except LiteralPatternConverter that actually use Configuration. LiteralPatternConverter has appropriate null checks.

[ppkarwasz]

@carterkozak: that should do it.

As far as I can see, no NPEs will result from providing null as configuration in the PatternLayout. I added a null check for the only case I found.

[carterkozak]

Great work, thank you for the contribution!