The select2 binding can be removed when used in repeating sections

[chrisala]

This is most easily reproduced using the RLP Outcomes Report 1 and RLP Outcomes Report 2.
To reproduce:

1. Open one of these reports
2. Add a new investment priority if there isn't more than one.
3. Observe the multi-select for Q 2b). At this point, both versions of 2b) may still have the correct select2 component.
4. Enter data into one of the select 2 components
5. Save the form and reload.

Expected:
All of the multi-selects have the select2 binding applied

Actual:
Only the final section (so the last Q2b) on the form still has the select2 binding, the other Q2b) is a regular HTML multi-select.

[chrisala]

My theory as to the cause is the jquery-validation-engine is applying the same id to all instances of the Q2b) element which causes problems with the select2 binding.
I am not currently sure why, but despite having the validation binding, the other select2 multi selects on the page don't have a jquery-validation-engine id applied so the problem with the select2 binding doesn't happen.

[chrisala]

Further investigation reveals that the cause (although the exact mechanism is unclear) is that the page attempts to validate the form when resuming a report with the "started" progress status (in order to allow the user to continue from the first invalid field).
This validation occurs before the data-binding initialisation is complete when there are pre-populations via ajax which appears to be the cause.
Adding a workaround to delay that first validation prevents this issue from happening.