Add warning in JCMA for Test Migrations that may report success despite partial migration due to tolerant migrations

Description
Users running Test Migrations in JCMA may assume that a “successful” status means a fully successful migration. With tolerant migrations enabled, this is no longer always the case, as migrations can complete successfully while still skipping or failing some entities. This creates confusion and may lead to incorrect assumptions about migration completeness.

Steps to reproduce (right now) / Actual Result:

Run a Test Migration in JCMA with tolerant migrations enabled
Allow the migration to complete

Actual Result:
The migration is shown as “successful” even if some items were not migrated. There is no clear warning or indication highlighting that the result may represent a partial success.

IMPACT

Users may proceed to production migrations without realizing that some data was not migrated during testing. This can result in incomplete migrations, rework, or unexpected issues post-migration.

What would improve if solved:

Introducing a clear warning in the UI would set proper expectations for users. It would encourage them to review migration logs and reports, ensuring they identify and address any skipped or failed items before proceeding.

Impact on stakeholders:

• Customers gain better visibility and understanding of migration outcomes
• Support teams face fewer tickets related to “missing data” after migrations
• Product teams improve user trust and reduce ambiguity in migration reporting