Fix IAMs showing erroneously on every cold start

[nan-li]

Description

One Line Summary

Fix IAMs displaying on every cold start when they shouldn't be (such as they should only display once or not meeting the time between redisplays).

Details

Motivation

Fix reports of this issue above.

Scope

The fix is to read in dismissed IAMs on IAM Manager start

• The IAM Manager holds a list of IAMs that have been seen and dismissed by the user called _dismissedMessages.
• We were not setting this list up when the IAM Manager starts, which led to this issue. Now we read it in on start()
• Because the _dismissedMessages list was always empty, redisplay data was not passed on to the fetched IAMs, so these IAMs believed they had never been displayed.
• See equivalent code on player model.

Testing

Unit testing

None

Manual testing

Android emulator API 33
Tested cold starts and backgrounding with these type of IAMs

• IAMs that are set to display only once
• IAMs with time gap between redisplays
• IAMs set to display on every app open

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