New tests that JsonIncludeAttribute and JsonNumberHandlingAttribute are honored during deserialization

[SkiFoD]

I added two test for checking the attributes during parameterized ctor deserialization.
ArgumentDeserialization_Honors_JsonNumberHandling test shows that JsonIncludeAttribute is not necessary when the deserialization occurs via ctor mapping even though the properties don't have setters.
This is the only thing that bothers me.

#47855

[ghost]

Tagging subscribers to this area: @eiriktsarpalis, @layomia
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I added two test for checking the attributes during parameterized ctor deserialization.
ArgumentDeserialization_Honors_JsonNumberHandling test shows that JsonIncludeAttribute is not necessary when the deserialization occurs via ctor mapping even though the properties don't have setters.
This is the only thing that bothers me.

#47855

Author:	SkiFoD
Assignees:	-
Labels:	area-System.Text.Json
Milestone:	-

[layomia]

Thanks for the PR @SkiFoD.

ArgumentDeserialization_Honors_JsonNumberHandling test shows that JsonIncludeAttribute is not necessary when the deserialization occurs via ctor mapping even though the properties don't have setters.
This is the only thing that bothers me.

I just realized that with the current implementation, the attribute is indeed not necessary. I updated my comment at #47855 (comment) to reflect this.

[layomia]

for variety, let this be one that has a private or internal setter.

[layomia]

Add another property that has a non-public accessor, without the attribute, to show that deserialization works regardless. Then, add a comment that says we should add another test for non-public members when #31511 is implemented.

[SkiFoD]

Thank you for your response @layomia. I made a new commit with the fixes.

[layomia]

Thanks!