Bail out for primary constructor parameters in IDE0059 analyzer

[mavasani]

Fixes #69643

We already did so for IDE0060 (unused parameters) in a prior PR. This adds a similar bailout check in the core dataflow analysis IOperation walker for IDE0059 (unused value assignment).

Verified that the added unit test fails with IDE0059 diagnostic prior to the product fix.

[CyrusNajmabadi]

Do we want to truly bail out? Or actually just analyze the entire class to determine if the parameters are unused?

[mavasani]

Do we want to truly bail out? Or actually just analyze the entire class to determine if the parameters are unused?

That would be a thing to consider for IDE0060 (unused parameters diagnostic). This PR is primarily for IDE0059 (unnecessary value assignment), which flags writes to locals and parameters in a method body for which there are no reachable reads. Given that PC parameters are basically fields, we don't know if any writes within a method body are unnecessary.

[mavasani]

Or actually just analyze the entire class to determine if the parameters are unused?

I am going to merge this PR to avoid this false positive. I'll file a separate feature request to consider adding functionality for flagging unused PC parameters.