Add discard parameter to preventDefault()

[emawby]

Description

One Line Summary

Add the ability to immediately discard a notification by calling preventDefault(discard: true)

Details

Adding an overload to the preventDefault method in theNotificationWillDisplayEvent and NotificationReceivedEvent that adds a boolean parameter discard

When true this parameter results in dropping the notification immediately instead of waiting to see if display()will be called within the next 30 seconds.

This is equivalent to calling the completion handler with no notification in the player model SDK.

Motivation

This fixes a bug/behavior where if the app is closed before the preventDefault waiter times out, the notification is not marked as dismissed in the local database and will be displayed when the app is next opened.

Scope

notification will display and received event handling

Testing

Unit testing

added unit tests to validate we don't wait for display() to be called prior to marking the notification as dismissed.

Manual testing

Tested the will display in foreground flow with discard both false and true. Verified that it fixed the redisplay on next open behavior.

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
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• 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.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is