Migration 158 Legacy Data Issues

[quoideneuf]

Adds 2 small modifications to the ARK migration adopted here: #2472

1. Ensure that duplicate "zombie" rows are deleted before and after the first big transaction.
2. Ensure that the user is warned and the migration is aborted if legacy data contains a one-to-many ARK-to-Resource relation.

Description

Related JIRA Ticket or GitHub Issue

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have read the CONTRIBUTING document.
• I have authority to submit this code.
• I have added tests to cover my changes.
• All new and existing tests passed.