fix(uve): scope radio and checkbox inputs by field variable name

[zJaaal]

Summary

• Radio buttons and checkboxes in the UVE quick-edit form were sharing the same browser input group across different fields, causing selections in one field to affect another
• Added [name]="field.variable" to p-radioButton and p-checkbox in the @for loop so each field's inputs are scoped independently by their unique variable name

Closes #35432

Test plan

• Open UVE and click a contentlet with multiple Radio fields — selecting an option in one field should not affect another
• Open UVE and click a contentlet with multiple Checkbox fields — checking/unchecking in one field should not affect another
• Verify single-option binary checkboxes still work correctly

🤖 Generated with Claude Code

[claude]

Claude finished @zJaaal's task in 1m 0s —— View job

---

PR Review

• Read changed files
• Review HTML template changes
• Review test changes
• Post findings

---

HTML change — correct and minimal. field.variable is already the reactive form key, so it's guaranteed unique within the form; using it as the name attribute is the right choice.

One thing to flag in the tests:

The behavioral isolation tests (form.get('sizes')?.value, form.get('status')?.value) verify Angular reactive-form isolation — but that layer was never broken. Each formControl is keyed by field.variable regardless of the HTML name attribute, so those assertions would pass even on the unfixed code.

The actual bug was browser-native visual grouping: two radio/checkbox groups sharing the same name in the DOM, so clicking one field's option would visually deselect another field's option. The regression tests that actually cover this are the getAttribute('name') assertions in the it.each blocks — those are the meaningful guards for this fix.

The isolation tests aren't wrong, they just don't prove what their comments imply. Not blocking, but a future reader might draw incorrect conclusions from the test descriptions.

Otherwise clean.