feat(radio): Radio element and radiogroup init

[cityremade]

Creates:

• ui element radio
• location entry radiogroup
• radio element stylesheet

Possible configuration requires at least 2 boolean fields meant to be mutually exclusive.

Checking one unchecks all others.

Use case: select model type and use only relevant input - conditionals within on change callbacks at a further stage.

{
  "field":"model_food",
  "title":"Model Type",
  "label":"Food",
  "type":"radiogroup",
  "edit":true,
  "radiogroup":{
    "name":"my_model_type",
    "caption":"Select model type to run for this site"
  }
},
{
  "field":"model_clothes",
  "label":"Clothes",
  "type":"radiogroup",
  "edit":true,
  "radiogroup":{
    "name":"my_model_type"
  }
},
{
  "field":"model_home",
  "label":"Home",
  "type":"radiogroup",
  "edit":true,
  "radiogroup":{
    "name":"my_model_type"
  }
}

[simon-leech]

The radiogroup should be almost identical to the text dropdown entry method but only allowing a single selection.

It should support getting the values from a query - it should support everything a text entry, does with the caveat you can only select one value :)

[cityremade]

Radiobutton is a boolean at its root. It only knows if it's on or off.
Think about it as a group of mutually exclusive checkboxes.

Value updates and callbacks should be handled with onchange radiogroup event and will be added later outside this pr.

[dbauszus-glx]

Can you resolve the merge conflict and the sonar cloud issues?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dbauszus-glx]

This doesn't match the specification of the ticket. I'd like to see the radio element first as a susbtitute for a single select dropdown element before creating a complex multiple related boolean fields use case and then finding a problem for this solution.