Collecting some build data for tasks/targets telemetry

[JanKrivanek]

[NOTE] - I'm experimenting with alternative approach - transfering the info once per build via dedicated event args

Fixes #10946

If split into separate PRs is prefered - please indicate so in comments

Goal

Obtaining information about build composition from microsoft versus 3rd party tasks and targets.

Approach

Since the information is present in the building worker nodes - the code collects it there and then (if requested) send it via ProjectFinishedEventArgs (one of few event args that are being transfered regardless of connected loggers) to the main node.

The classification of 3rd party versus 1st party is for simplicity being done based on location of defining msbuild project and naming of the assembly.

Changes

• Added class for the exexution statistics of tasks - this is contained in TaskRegistry as well as in TaskFactoryWrappers
• RequestBuilder is the orchestration here, that decides whether statistics are needed and if yes - traverses the TaskRegistry, BuildResult and ProjectCollection in order to accumulate and populate the statistics
• ProjectFinishedEventArgs holds and transfers the statistics. They are only preserved during runtime - binlog de/serialization is intentionaly not added.

Performance considerations

By default the data collection logic is off and hence statistics are not collected on worker node, nor serialized to the event args. The perf impact of collection and serialization was though beyond the recognition level of basic 'full duration' testing of full and incremental build of small console and bigger size projects.