[release/8.0] Throw when applying JsonObjectHandling.Populate to types with parameterized constructors.

[github-actions]

Backport of #92937 to release/8.0

/cc @eiriktsarpalis

Customer Impact

We received a customer report that the newly added JsonObjectCreationHandling feature (aka "populate read-only members") does not behave as expected when applied to types that deserialize using parameterized constructors. On closer inspection it turned out fixing the feature for that particular use case would necessitate substantial refactoring of async serialization code, something that is too risky/time consuming to do at this stage. Instead, this PR adds checks and throws an explicit exception when users attempt to use the feature on types with parameterized constructors.

Testing

Added unit testing validating the throwing behavior.

Risk

Low. Adds additional validation to product code to block the unsupported scenario.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #92937 to release/8.0

/cc @eiriktsarpalis

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	area-System.Text.Json
Milestone:	-

[artl93]

@eiriktsarpalis - is this something we'd want to change later to add parameterized constructor support? (e.g. 9.0, servicing, never?)

[jeffhandley]

@eiriktsarpalis - is this something we'd want to change later to add parameterized constructor support? (e.g. 9.0, servicing, never?)

We are leaving it in the backlog (#92877) as something we will consider adding support for in .NET 9+. We would not bring it for servicing though.

[carlossanlop]

Approved by Tactics via email.