Issue Description

When running pre-migration checks in the Jira Cloud Migration Assistant (JCMA), results from previous executions can appear in subsequent runs due to the caching mechanism used by the tool.

Even after deleting an existing integration and creating a new one from scratch, previously generated log files and reports may still appear in the check results. This behavior makes it difficult to distinguish between outputs generated by the current run and those from earlier executions.

In practice, the only reliable way to obtain a completely clean set of pre-migration check results is to create a new migration plan with a different name, which forces JCMA to execute the checks again instead of reusing cached results.

Steps to Reproduce

1. Delete the existing JCMA integration.
2. Create a new integration from scratch.
3. Run pre-migration checks.
4. Observe that log files and reports from previous runs are still displayed in the results.

Expected Behavior

When running pre-migration checks after recreating an integration or starting a new migration preparation cycle, only results generated during the current execution should be displayed.

Ideally, administrators should have a way to:

• Clear cached pre-migration check results

• Isolate results per migration run

• Or explicitly force a full re-run of all checks without reusing cached data

Actual Behavior

Logs and report files from previous runs are still visible after creating a new integration, causing confusion and making it hard to validate the current state of the migration checks.