Remove nullable return from ConstructorInvoker.Invoke()

[steveharter]

The nullability for recent issue #88415 was incorrect for ConstructorInvoker's Invoke() return value - it shouldn't be nullable.

This is unlike ConstructorInfo.Invoke() which can return null if the incoming obj parameter is non-null in which case the constructor is called on obj without allocation. Since ConstructorInvoker doesn't have an obj parameter, it will always allocate and return an object (and call the constructor on it).

Mail sent to FXDC for approval request.

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[ghost]

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

Issue Details

---

The nullability for recent issue #88415 was incorrect for ConstructorInvoker's Invoke() return value - it shouldn't be nullable.

This is unlike ConstructorInfo.Invoke() which can return null if the incoming obj parameter is non-null in which case the constructor is called on obj without allocation. Since ConstructorInvoker doesn't have an obj parameter, it will always allocate and return an object (and call the constructor on it).

Mail sent to FXDC for approval request.

Author:	steveharter
Assignees:	-
Labels:	area-System.Reflection, new-api-needs-documentation
Milestone:	-

[jkotas]

LGTM