Issue Summary

Currently, getPaginatedMapping(namespace, pageSize) on AppCloudForgeMigrationGateway returns cumulative mappings from all previous migrations, not just the current transfer.

This makes it impossible for apps to distinguish which entities (e.g., dashboards via jira:portalPage) were migrated in the current transfer vs. previous ones.

We need either: (1) a transfer-scoped variant of getPaginatedMapping that returns only mappings for entities migrated in the current transfer, or (2) an API that returns the list of entity IDs (e.g., dashboard IDs) that are part of the current transfer's migration scope.

This would allow apps to process entities that exist in mappings but weren't part of the current migration. 

 Workaround

 Currently there is no known workaround for this behavior. A workaround will be added here when available