Retry migration if it didn't fully complete
### End goal At the end, users should be able to re-run migrations that didn't completed fully and successfully - some items of imported groups and projects failed to import. It should be possible from UI. _User comment: "If it fails (which could happen if connection is lost between instances), I would like to have the ability to just trigger that particular import again until it finishes without errors."_ ### Plan We will start with enable users to retry parts of migration that failed - at first chosen relation for a chosen project. We build up from there, allowing projects retries, then whole group retries. The retry will not create a new project/group (this option we have now, with Re-import button on for the top-level groups available for import), but will append previously not imported items to already existing projects and groups. ### UX The aim is to allow the re-import from UI. We start with endpoints allowing for re-importing chosen relations (out of few selected) to a chosen project. No UI included. There's many questions considering UX: - In UI, on what level(s) can we allow for re-imports (relations, projects, groups, all), so that it doesn't confuse the user? - There's `Re-import` button on top-level groups level at the moment, as described above - what to do not to confuse two different options? - How and where to show the result of the re-runs? ### Assumptions Users should not perform changes in source projects/groups between import and its re-run.
epic