ConflictResolver.ResolveConflict is ~3.3% of all allocations in solution-wide design-time build

[davkean]

[ericstj]

Bigger question here is why does this reference graph result in conflicts? We should do work to ensure packages are moved forward to provide dependency groups that don't pull in old packages (and thus excessive downloads and conflicts).

I would expect a "happy path" project to never call this method.

Barring that, some work could be done to avoid excessive string allocations here. I would imagine that would mean using more LogMessage overloads with formatting parameters that let the logger decide if it needs to format the string (allocating) or not.

[nguerrera]

This might be fixed with @eerhardt's changes.

[nguerrera]

Fixed by #1805