Remove duplicated RadioButtons page

[Zakariathr22]

Description

Main changes are;

• Moved the example from the RadioButtons page to the RadioButton page
• Removed the redundant RadioButtons page
• Updated ControlInfoData.json accordingly
• Removed RadioButtons.png from assets

Motivation and Context

• closes Duplicate RadioButtons sample in Basic Input and Layout sections #2068

How Has This Been Tested?

Manually tested

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

[niels9001]

I wonder why we had this in the first place. Probably because RadioButtons was added later on?

Anyways, great work! Tested, and approved!

[niels9001]

/azp run

[marcelwgn]

/azp run

[marcelwgn]

I think we should converge into the RadioButtons page instead of RadioButton. There are very little use cases for the RadioButton control (without s), you would probably almost always use a RadioButtons control. Before RadioButtons, RadioButton was the only option and it did some grouping via key logic and walking the tree (iirc), but now thats no longer necessary. RadioButtons is the easier and better option for most scenarios.

[Jay-o-Way]

Suggested change

	"Description": "Use RadioButton controls to let a user choose between mutually exclusive, related options. Generally contained within a RadioButtons group control.",

To differentiate between the two very different items

[Jay-o-Way]

Did we lose this link?

[Zakariathr22]

I think we should converge into the RadioButtons page instead of RadioButton. There are very little use cases for the RadioButton control (without s), you would probably almost always use a RadioButtons control. Before RadioButtons, RadioButton was the only option and it did some grouping via key logic and walking the tree (iirc), but now thats no longer necessary. RadioButtons is the easier and better option for most scenarios.

@marcelwgn, should it be in the controls section or the layouts section?