Log item Includes, Removes and Updates during evaluation

[KirillOsenkov]

One of the biggest missing features in logging that keeps hurting us is we don't log item includes, removes and updates during evaluation, with the source location where it happened.

We do log the final set of all items after evaluation is done, but it is currently impossible to see where a specific item was added during evaluation.

We should consider logging a TaskParameterEventArgs perhaps (even though the same is not the best fit semantically), because we already have all the infrastructure for items that are logged during target execution. We can reuse the same infrastructure during evaluation as well.

One potential pitfall here is perf, so need to be careful and measure eval perf before and after. Maybe only do this when the binary logger is present.

This is in complement for the similar request for properties:
#2711

[AR-May]

Team triage: it seems that we will need to fix this for the BuildCheck user story too. Let's add it there as an item.

[danmoseley]

I would expect perf will indeed be a problem.

[JanKrivanek]

We will experiment with analgous data for props (possibly as part of, or continuation of #10009) - I'd hope that if we accumulate and properly deduplicate/compress the info (especially the names and locations, that will largely repeat) and then send everything in a single blob, the perf might not get that big of an impact. If it's still a deal breaker, than we can scope it only to the user code (the term is yet to be exactly defined) in the default mode.