[redcap] bulk importer

[regisoc]

Brief summary of changes

This PR adds a new tool to bulk import data from REDCap linked instances/projects.
It will be mostly useful for retrospective data, or to do targeted batch import.

Multiple caveats and todos:

• arguments need to be defined. There are in the script for now.
• difficult for me to test as is, I need to make some edits/overrides for ibis to actually use it (difference in instrument names between LORIS/REDCap).
• I purposefully let some code as comments, these snippets are already tested and might be useful if we decide to wrangle on event/instruments names.
• REDCap has a event-instrument mapping endpoint, that conveniently has the unique_event_name and the form_name . I used the LORIS corresponding class to get these two, but again, that only works if the names are exactly the same on both ends (LORIS and REDCap).
• Participant IDs/Record IDs will also need mappings I guess if they are not clearly the same on both ends.
• we can add restrictive arguments later.

Link(s) to related issue(s)

No related issue.

[MaximeBICMTL]

Thanks for tackling this work! I will do a deeper review once the PR is out of draft. Just a few small comments based on what I am seeing now.

I will quickly say that I prefer snake_case to camelCase, but this is non-blocking, and LORIS uses both namings anyway (and even some others...).

[MaximeBICMTL]

This return type is too complex IMO. I would prefer to return a simple list of RedcapConfig. The caller can handle special cases like the empty list itself, and the instance URLs and project IDs are available in each RedcapConfig if needed.

[MaximeBICMTL]

Ideally I guess I should refactor the parser to more elegantly handle the "get all project configurations" and "get single project configuration" cases, but this is out of scope for this PR, your code is fine 👍