FIO-7225: Fixed issues with complex values for Radio component

[roma-formio]

Link to Jira Ticket

https://formio.atlassian.net/browse/FIO-7225

Description

Issue: Using the radio component with a URL data source and complex data types (such as objects or arrays) as values can lead to incorrect behavior and visual bugs, such as missing labels in submissions. The problem arises because the radio component should use string values in HTML, and the current implementation uses toString to convert values to strings, which can result in the string representation [object Object], making it difficult to track the original value.

Solution: If the value type differs from a string, create a values mapping (unique generated string -> original value) and use the unique generated string for the value of the HTML radio input. Any further updates from HTML or programmatically will involve checking the values mapping and restoring original values if necessary. This approach allows the radio component to handle any complex value structure and ensures that the original values are preserved and correctly mapped back when needed.

How has this PR been tested?

Unit testing

Checklist:

• I have completed the above PR template
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• My changes include tests that prove my fix is effective (or that my feature works as intended)
• New and existing unit/integration tests pass locally with my changes
• Any dependent changes have corresponding PRs that are listed above