[Instrument] missing error message when Linst Form won't save due to BasicDate field

[christinerogers]

When a BasicDate field is required due to a Xin rule, and left empty, and the Linst Form (correctly) doesn't save --
the user has to re-check every field in the form because no error message appears near the BasicDate field.

This is frustrating to users and may lead to data loss.

e.g. in this sequence of questions :
(1) Was the Surgery done? (yes/no/not_answered) -> user selects "yes"
(2) What date was the surgery? (BasicDate) --> left empty.
And there is a XIN rule in place: (2) date is required iff (1) surgery done== "yes"

In this case, the XIN rule triggers correctly, and the Form doesn't save (correctly) and an error message is printed at top (Form was not saved) -- but there's no way to tell which field caused the error.
The user has to re-check every field in the form.

Note StandardDate can't be used instead, because of another bug #7650

[christinerogers]

might be resolved by #7266 - to be verified

[ridz1208]

@christinerogers was it verified ?

[christinerogers]

I haven't tested on main, but as an override on a 23 install this pr fixed the issue.