Properly support different FromBody.AllowEmpty settings

[captainsafia]

The FromBody attribute currently accepts a boolean allowEmpty value that allows the developer to determine whether or not the route will accept an empty body as part of the request.

The attribute currently assumes that both EmptyBodyBehavior.Default and EmptyBodyBehavior.Disallow map to allowEmpty = false which is problematic when we want to discern scenarios where a developer explicitly set the allowEmpty parameter vs scenarios where we are using the implied value.

We'll need to update the codepath to discern when a user set the AllowEmpty attribute to support overriding the optionality configuration that was inferred from the code.

See #34505 (comment) for more info.

[ghost]

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.