Jira Cloud Migration Assistant 1.5.8 user/group migration is not evaluating which users/groups to migrate correctly

Issue Summary

Jira Cloud Migration Assistant doesn't appear to be evaluating which users/groups to migrate correctly. The preflight checks evaluate an inaccurate number on Jira Cloud Migration Assistant version 1.5.8 and higher.

Steps to Reproduce

1. Create a Jira Server with users in the internal directory. Run counts from the database and validate how many users you have
2. Set up a test migration plan and note that the counts returned appear to be consistent with the counts returned from the database
3. Set up an upstream Crowd Server and Import test users to Crowd Server via CSV
4. From Jira Server, integrate with upstream Crowd and sync down the users
5. Run counts from the database and note that your total user count has increased by the test users you've synced from Crowd
6. Set up another test migration plan with Jira Cloud Migration Assistant 1.5.8

Expected Results

Jira Cloud Migration Assistant will calculate the user/groups correctly by evaluating both the internal and external directories since they are both active.

Actual Results

The migration plan is not picking up the users that have been synced to the Server. You can verify this by comparing the counts found in preflight vs the counts returned from cwd_user DB table in Jira Sever. Restarting Jira Server nor clearing the context app cache changes this behavior.

curl -X DELETE -u charlie <HOST>/rest/internal/1.0/cache/app

1. Uninstall Jira Cloud Migration Assistant 1.5.8 and install Jira Cloud Migration Assistant 1.5.7 from the marketplace
2. Create a new migration plan and notice that the counts are accurate once more.

Workaround

1. Uninstall Jira Cloud Migration Assistant 1.5.8 and install Jira Cloud Migration Assistant 1.5.7 from the marketplace
2. Have Migration Support enable a feature flag to bypass the Jira Cloud Migration Assistant upgrade check.