Remove redundant creation of Forwarding logger with NullLogger

[JanKrivanek]

Context

Random discovery - we create NullLogger even when we have other logger(s) registered (e.g. ConsoleLogger, TerminalLogger ...).

We need to make sure that Projcet started and finished events are being transfered - we can 'hijack' the existing registration of ConfigurableLForwardingLogger for that - we just need to inspect and adjust existing registration

Motivation

Build with just the built-in loggers (TerminalLogger, ConsoleLogger, FileLogger) is probably the most common configuration - and we are injecting extra forwarder to each such a build - so while it's likely very small savings (as only couple events was redundantly de/serialized, rest was quickly skipped) - it applies very broadly.

Perf

Following measurements were done using the OrchardCore and bootstrapped release MSBuild.exe with following 3 scenarios:

• MSBuild.exe -m
• MSBuild.exe -v:m -m
• MSBuild.exe -tl -m

Each scenario for each branch for 3 runs after the warmup run. Clean and kill of msbuild/dotnet/vbcscompiler processes between each individual runs. Median value choosed for each scenario.

The versions that has been tested were:

• main (a8e224f)
• Logging Svc fix (This PR)
• Expanders refactor (Expander refactoring [property tracking analyzers prerequisity] #10102)

	MSBuild.exe -m	MSBuild.exe -v:m -m	MSBuild.exe -tl -m
Main	00:00:36.02	00:00:31.86	00:00:33.22
Logging Svc fix	00:00:35.57	00:00:30.89	00:00:33.79
Expanders refactor	00:00:36.66	00:00:32.43	00:00:32.49

Testing

Pre-existing tests