JWT: Resolve IAM conditions after user create to allow fetching of IAMs

[nan-li]

Description

One Line Summary

Resolve fetch IAM conditions after the user create call, not just in user update call, in order to allow fetching IAMs after the first usage of login.

Details

When Identity Verification is enabled, the initial anonymous user create is dropped. As a result, we will never make this call. Then, when login is invoked, we send a create user request with no subsequent update user calls to be made. Thus, the fetch IAM condition was never resolving. Since create user returns ryw data from the server, we can safely resolve the condition with this data when the create user returns successfully. Additionally, this is appropriate and safe to do so as a create user call effectively serves the same role as a user update call for purposes of read-your-write consistency.

Motivation

• Reported in [Question]: InAppMessagesManager.evaluateInAppMessages() not proceeding when a trigger is sent. #2336 and reproducible

Scope

• Add resolving fetch IAM conditions after user create
• Behavior change: Does result in a behavior change when combined with Fix: IAM not shown when calling login immediately after init #2287. When a new user logs in, IAMs may be fetched again if enough time has passed since the initial fetch at app start.
• remove a chunk of code leftover from Fix: IAM not shown when calling login immediately after init #2287 that was left over after rebase

Testing

Unit testing

Unit tests are updated only

Manual testing

Android emulator on API 35
Reproduced the issue that IAMs are not fetched after the first login call. After fix, IAMs are fetched.

Testing with identity verification enabled:

1. New install, then login, iams fetched
2. Quit and reopen app, patch user call is made for new session, iams fetched
3. Now login to another user, iams are fetched again if enough time has passed since the last fetch

Testing with identity verification disabled:

1. New install, iams are fetched for the anonymous user
2. Now login to another user, iams are fetched again if enough tie has passed since the last fetch
3. Now logout (blocked: logout appears broken when identity verification is disabled)

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is