Extract FileInputComponent as it's own ckanext

[ChasNelson1990]

Contact Details

chas@fjelltopp.org

Problem

We currently have the same JS source code across four projects. As we are now adding this to this repo it's an opportune time to extract it for future use.

Solution

• [ ] Pull out the JS, CSS and Jinja for the FileInputComponent into it's own ckanext.
• [ ] Add that ckanext to fjelltopp-infrastructure group vars for zarr-ckan, who-afro-ckan and who-romania-ckan (possibly by creating a shared funicular.ini config too)
• [ ] Remove any left overs, e.g. web assets, etc.

Considerd Alternatives

@tomeksabala and I did discuss the following:

• Using CKAN's preferred JS JQuery module system - we don't want to be locked into such an old system
• Extracting purely JS and CSS and requiring projects that use it to add two lines to templates (<script/> and <div id="*"/>)

[ChasNelson1990]

We have also asked on https://gitter.im/ckan/chat what the long-term overheads of having lots of small ckanexts could be