[redcap] repeated field ordering and configuration

[regisoc]

Brief summary of changes

This PR:

• adds a new configuration for the repeated instrument index field choice at project level.

  • Imported repeated records will be ordered automatically based on the chosen field (defaults to repeat_instance, and timestamp still available).
  • <redcap-repeat-id>repeat_instance</redcap-repeat-id>

• bugfixes the repeated record case. Cause/chain of events:

  • All repeated records were downloaded at once when using the import script.
  • the change introduced in the REDCap importer and associated script was missing the repeated instrument logic.
  • The original "timestamp"-based ordering + index increment was scrambling the records order and we ended up with thousand of unrelated index numbers (e.g. Q1K case).
  • The fix isolates the "bulk" i.e. script import process (client::getInstrumentRecords(record_id = null)) from the single record import when receiving REDCap notification (client::getInstrumentRecords(record_id != null)).

• Have you updated related documentation?

Testing instructions (if applicable)

1. have a REDCap set up that includes repeated instruments.
2. import of single REDCap repeated instrument: trigger one repeated instrument import (notification class path).
3. import multiple REDCap repeated instruments (single event): trigger the REDcap importer tool (bulk import path).

[MaximeBICMTL]

I really like the idea of using redcap_repeat_instance to get the index of a repeated instrument record (that's basically what I had in mind when I wrote the TODO comment). Do we still also need the timestamp-based approach though? If we only have the former we can always know the index of a repeated record independently of other records, which is a lot cleaner IMO (and allows us to get rid of the RedcapRecord inheritance hierarchy eventually)

[ridz1208]

@regisoc has this been updated according to the latest discussion ?

[regisoc]

@ridz1208 not yet in sync.
@MaximeBICMTL I still want to have the timestamp option, as we discover new way of handling REDCap data. The problem on the timestamp is because of user error. In a project, some users are entering data as admin which is skipping the init of multiple fields... and in any case, I made redcap_repeat_instance as the default.

[regisoc]

@ridz1208 repeated instrument logic in sync.
It includes both https://github.com/aces/CBIGR/pull/822 and the bugfix https://github.com/aces/CBIGR/pull/873.
The add-instrument feature is not included. Another PR needs to be sent.