fix(radio-group): value handling

[olaf-k]

This short PR attempts to fix the radio-group's value setting.

In the current code, inferring a radio-group's initial value from a checked radio child does not work properly:

• the form's value is not set
• the radio-group is not focusable (because all its radios get -1 tabindex)

Both of these behaviors stem from the fact that the value setter's logic is not called. This PR corrects that by triggering it in the slot change handler.

I've also taken the opportunity to:

• remove Updates.enqueue from this handler as it defers the component initialization (first call to radiosChanged) to the next event loop tick, which is not great UX if authors want to get the value early (e.g., in a whenDefined call).
• replace direct calls to checkRadio() by radio.click() in radio-group so that keyboard navigation would also emit the proper events.
• fix the default validation messages copied from the native element (radio had the one from checkbox and radio-group lacked the mandatory name prop).
• make said default validation message static.

(Not related but, for some reason, there is code that unchecks a radio when it becomes disabled. I'm not sure that's wanted as it is a strange departure from native behavior, so I also removed that.)
I reverted the "disabled unchecked" change as I learned the hard way the Fluent component is designed to work this way. (I rewrote the logic for my own component, let me know if you're interested in another PR for that).

[chrisdholt]

Adding @radium-v to review, thanks @olaf-k!

[github-actions]

📊 Bundle size report

✅ No changes found

[github-actions]

Pull request demo site: URL