JCMA appends (migrated) to entites that are already existing only as team-managed

Issue Summary

Per this kb article,

• If an entity in your migration has the same name as an entity in the cloud site, and we have a record of migrating it, we will link your data to the existing entity in the destination site. We will not re-migrate this entity.

• If an entity in your migration has the same name as an entity in the cloud site, and we don't have a record of migrating it, we will modify the name by adding (migrated) to avoid duplicates and ensure there's no data loss (we cannot guarantee that a field with the same name is exactly the same field). For example, an entity called Custom field A will be renamed to Custom field A (migrated) after migration.

Entities that are a part of existing team-managed (next-gen) projects both exist and do not exist. While they have records in the database, it is not an entity that the customer cares about or can see in regard to company-managed (classic) projects. This creates confusion and unnecessary complication.

JCMA appears to be comparing against all entities, including team-managed.

Steps to Reproduce

1. Create a team-managed project in cloud with custom field "Example Field"
2. Create a project on DC and add a custom field by the same name "Example Field"
3. Migrate DC project to Cloud
4. Observe Custom Field name for the migrated company-managed project in cloud "Example Field (migrated)"

Expected Results

The entity is created using the original name. (Without "(migrated)")

Actual Results

JCMA appends "(migrated)" to the field

This may apply to other entities as well, not only custom fields.

Workaround

Rename or merge the entity post migration.