[BuildCheck Suggestion]: Flag usage of the Properties metadata on inputs to the MSBuild Task like ProjectReference

### Summary

This is almost never correct - per-project Properties completely override the Properties on the MSBuild Task invocation itself - what is almost certainly intended is the use of AdditionalProperties on the input Projects to _add_ to the set of global properties.

### Background and Motivation

Internal discussion thread where users are setting Properties directly and then having lots of downstream problems with managing the projectreference protocol

### Sample issue or antipattern that the check should be flagging

Any use of Properties on a ProjectReference - especially those setting Configuration, TargetFramework, or Platform

### Sample output

_No response_