[redcap] new module

[regisoc]

Brief summary of changes (WIP)

This PR adds the REDCap interoperability module.
This module opens an API endpoint to receive notifications from REDCap servers through the use of the Data Entry Trigger (DET). REDCap notifications are parsed and REDCap records are imported into LORIS.
If an error happens during this notification handling process, an error is generated in the issue tracker.
The module is imported from HBCD, and even if the core logic is the same, REDCap objects are now their own models.
This version also supports connection to multiple REDCap instances.

Features

The main goal was to replicate HBCD data import process based on REDCap DET.

• Refactoring of the REDCap HTTP Client and linked classes/models.
• Support for multiple REDCap instances.
• Additional tools and features:
  • redcap2linst: script to import REDCap forms as LORIS LINST instruments.
  • fetch button: UI button on instrument panel to trigger data import (could be done later)

State

• core module
• tools
  • redcap2linst adapted from HBCD usage (originally from Add script which converts a REDCap data dictionary to LINST format #8181). Added possibility to generate LINST instruments from different REDCap instances and files.
• documentation
• tests
  • automated test
  • test plan
• RB configuration
• additional features:
  • instrument fetch button (HBCD added feature) - UI button in the side panel of an instrument to trigger the import of data. Could be done in a later PR.

Testing instructions (if applicable)

Notification process:

1. Define main assignee, REDCap instances and projects in the config.xml following the structure given in RB/config.xml file.
2. Define which instruments could be imported by adding them to the configuration list in LORIS. See Front-end > Admin > Configuration > REDCap > redcap_importable_instrument.
3. Send a URL notification to LORIS (i.e. endpoint /redcap/notifications) to simulate the reception of a DET notification. The payload should be the following (see redcap/notifications/redcapnotification.class.inc):

{
    "instrument":"instrument_backend_name",
    "project_id":"REDCap project ID",
    "project_url":"REDCap project URL",
    "record":"REDCap record ID / PSCID",
    "redcap_event_name":"REDCap event name",
    "redcap_url":"REDCap instance URL",
    "username":"REDCap username",
    "${instrument_backend_name}_complete":"2"
}

REDCap LINST instrument process:

• See tools/redcap2linst.php usage.

Link(s) to related issue(s)

• RedCAP Interoperability in Core #9473

Links to related PRs

• Add script which converts a REDCap data dictionary to LINST format #8181
• [instrument_builder] REDCap 2 LINST #8282 (need to check)