feat/HIT-340-Kobo-import-collected-data-submissions

[estelafs]

Description

Branch created from the branch #92

Added kobo property in the Form model: to save kobo info on forms imported from kobotoolbox (id, deployedVersionId and apiConfiguration)

Created SynchronizeKoboModalComponent: modal available at the actions column in the Forms table if the form was made from the Kobotoolbox. Modal allows the user to set if want to import only submissions from the same form version that when the form was created on Oort or all data regardless of the version and also has a button to synchronize the data

Useful links

• Please insert link to ticket: https://oortcloud.atlassian.net/browse/HIT-340
• Please insert link to back-end branch if any: feat/HIT-340-Kobo-import-collected-data-submissions oort-backend#55

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (refactor or addition to existing functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

As described in the attached video

Screenshots

import-data-from-kobo.webm

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145