When migrating C2C, historical conflicts are presented as key conflicts, without including the reason

Issue Summary

When doing a C2C migration, the preflight check "Project already exist in Destination" triggers but when looking at the CSV report, the project key and name are different between the source and destination.

Even when the project from source and Destination are completely different and had never been on the same instance.

This is reproducible in Data Center: no

Steps to Reproduce

1. Have a project in the Destination with the same key as one of the source.
2. Change the key of the Destination
3. Create a migration plan to the destination and run the prechecks
4. Notice that the project already exists will trigger and the CSV file will show that pkey and project name a completely different

The issue seems to happen because the precheck validates for historical pkey of projects.

Expected Results

The report will include historical keys if historical keys are the reason for the conflict.

OR

The pre-flight check will resolve the conflict somehow, by erasing the historical key of one project or the other.

Actual Results

Pre-check will fail, and give a CSV file where the source project and destination project are completely different, and changing the pkey or name on the destination doesn't resolve the validation. This leaves the user with no information about the failure and no solution to resolve it.

Workaround

Option 1: We can move the issues in the destination project to a newer project. And then trash this project so that the key gets deleted. And then migrate the source project which should get migrated as is without any conflicting key. (this is when you have an active project with the same key on the destination site)

Option 2: Move the issues from the source project to a new empty project XYZ. Migrate this XYZ project to the destination. Move back the issues from XYZ to original project. This means the project will get migrated but with a different key.