Support of built-in Input components to work outside `EditForm`

[uabarahona]

Description

<InputRadioGroup> and <InputRadio> are awesome components that lets you bind to a unique "property", but using radio and radio-group does not necessary means we want to have form, a common scenario for radio button (with CSS) is to use them to show and hide certain parts of the website, or present the user different real forms.

Describe the solution you'd like

It might be relevant only for <InputRadioGroup> and <InputRadio> to work outside <EditForm> but I believe is worth exploring the idea to make other built-in input component work outside too.

I will definitely update this issue if I found more scenarios where other built-in inputs needs to work outside EditForm

[pranavkm]

@huunab this should be fixed as part of .NET 6: #35640 #27804

[uabarahona]

@pranavkm awesome! although it seems that the PR is targeting .NET 7 preview 1, also JIC I am working .NET 6 RC2 for all the feature request I am adding :D

[javiercn]

@pranavkm I checked and this change is not in 6.0 for some reason.

This is the commit that got merged on main afacc87 and git merge-base --is-ancestor afacc87 release/6.0 is returning a non-zero exit code, which means is not an ancestor.

@mkArtakMSFT I think we would like to backport this change, since it was originally scheduled for 6.0 and impacts libraries like the Blazor Fast components for fluent UI

[mkArtakMSFT]

Looks like this is a dupe of the issue which is fixed already. We'll evaluate whether we can bring this in 6.0 this late, or not.

[uabarahona]

@javiercn @mkArtakMSFT Thanks! will be waiting for this

[mkArtakMSFT]

Hi. I wanted to drop an update on this issue.
As @javiercn has pointed out above, we've been hoping to bring this fix for 6.0, but given how late during 6.0 release cycle this was done, we had decided that it is better to delay it till .NET 7. One of the major reasons for such decision was the complexity of this change and the risk involved with bringing it in this late.
That said, we're going to monitor this area closely in the near future, to gauge whether the interest here is high enough to warrant reconsideration, at which point we may choose to ship this as part of a .NET 6 patch release).