[redcap] REDCap UI

[regisoc]

Brief summary of changes

This PR adds a UI for designated users with new permission redcap_ui_view.

The UI is mainly targeted at people managing REDCap data integration, and adapts to one or multiple connected REDCap instances and projects.
The current UI composed by 3 tabs (more can be added) to give information and help navigate, this is particularly useful for issues arising when importing REDCap data e.g. missing notifications, network issues, out-of-sync instruments dictionary.

Images of current included tabs

Notifications received:

REDCap Dictionary in use:

REDCap import issues in issue tracker:

This PR also updates the redcap2linst:

• location to module/redcap/tools as a module specific tool.
• process to include an automatic redcap_dictionary table update when parsing the redcap dictionary.

To discuss:

• Caveat:
• Extract REDCap issues from issue tracker to their own "log-like" table/structure. As there can be a LOT of issues created under classical import conditions, or even in mass import cases, it could be useful to extract the REDCap issue process creation to some other structure or another table.

Testing instructions (if applicable)

1. Activate the redcap module in modules manager.
2. Go to Tools > REDCap menu item.

[MaximeBICMTL]

I know this is just a work-in-progress, but I did a small review notably of the Javascript side.

I know this requires some work, but I would heavily prefer to use Typescript and function components for the UI, untyped JS and class components are a lot harder to maintain in my opinion and I would rather not have them in newer code.

This is my main concern, outside of that, all the nits do not need to be addressed, those are just me stating my opinions on some pieces of code.

[MaximeBICMTL]

I am not sure about passing these values as props to the module.

• The first two can be obtained from the loris instance, no need to use props IMO.
• The latter one is not used right now (but I guess that may change).

[MaximeBICMTL]

Maybe just use data !== null instead of isLoaded ?

[MaximeBICMTL]

I don't think this.state.data can ever be null, it is initialized with an empty object {} or a JSON received from the back-end. I would also avoid loose equality in our code (use === instead of ==).

[MaximeBICMTL]

I would avoid putting constant data in a component state, I would rather use loris.BaseURL directly.

[MaximeBICMTL]

Same comments about constant data in state and isLoaded.

[MaximeBICMTL]

I would use return directly in the match switch instead of putting things in result, using break, and then returning.

[MaximeBICMTL]

Same comment about constant data.