JCMA is creating duplicate permission schemes

Issue Summary

When the projects are sharing the same permission scheme but have different sets of "User and roles", duplicate permission schemes will be created.

Steps to Reproduce

1. Create a new permission scheme, Scheme A, grant different roles to "Browse projects" permission. ie, Administrators, Developers, Users
2. Create 4 different projects, make sure they are using the same permission scheme
3. Edit "Users and roles" for each project:
   • On Project A, set a user/group to only "Administrators" role
   • On Project B, set a user/group to all 3 roles: Administrators, Developers, Users
   • On Project C, set a user/group to 2 roles: Administrators, Users
   • On Project D, set a user/group to 2 roles: Administrators, Users
4. Attempt to migrate these 4 projects to Cloud, using JCMA.
   • Users and groups: All users and groups
   • Group membership: Preserve group membership

Expected Results

Only 1 permission scheme is created because the projects are sharing the same permission scheme.

Actual Results

3 permission schemes are created, for each set of "Users and roles".

Workaround

Option 1: Migrate in two steps (This will be the default behaviour after Duplicate fix for Permission Scheme entity) - Recommended

• First migrate all the projects of type Business (Attachment Test, Business, Migration, Test Issue Linking) followed by migration of Software project (TEST). 
• This will create only two new permission schemes for the customer as shown in Screenshot3. 
  

Option 2: Modify the permission grant 

• Update the permission grant for Manage Sprint permission in the Permission scheme to remove all the values from the Granted to section as shown in the screenshot4. 
  
• Migrating all the projects in a single plan. In this case all the 5 projects will be mapped to single permission scheme as shown in screenshot5.
    
• Update the Manage Sprint role in the permission scheme migrated on cloud. (Important)