Fix/enhance validation messages on repeating groups

### Description

With the implementation of `minCount` on repeating groups, we need to be able to inform the user in an clear an accessible way. This might be an opportunity to look into how validation behaves and looks on repeating groups.

## Case 1 - Correct feedback to the user
The validation text need to reference the field it is validating. How do we solve this with groups where there may not be an identifying text to use.

## Case 2 - Validate the whole group
If there are a `minCount= 2`and the user has created one group. We only have a way to validate on groups. Maybe we need a way to show visually that it is missing a group.

## Case 3 - Difference between open and closed groups
We might need to ways of showing validations based on if the group is open when the validation happens.

### Additional Information

_No response_

### Tasks

_No response_

### Acceptance Criterias

_No response_

No files or tests are named. Start by tracing the existing minCount and repeating-group validation behavior, then compare feedback for the three cases described: identifying fields, missing groups, and open versus closed groups; done requires agreed accessible validation behavior for each case.

Written by the indexing model from the issue text.