[Fix] Outcomes IndexedDB schema

[jkasten2]

Description

1 Line Summary

Fix errors saving clicked outcomes due to keyPath value changed incorrectly.

Details

We are doing the following indexedDB table renames in this commit:

• NotificationClicked -> Outcomes.NotificationClicked
  • Correcting keyPath to "notificationId" in the new table.
• NotificationReceived -> Outcomes.NotificationReceived

Modiviation

Fixes the notification click direct outcomes feature. Also it is unknown if the indexedDB errors are causing throwing that is resulting in any other side-effect issues due to errors not being caught.

This is done to correct the keyPath for the "NotificationClicked" indexedDB table, you can't change it so a new table must be created.

Background

Table was created with wrong keyPath of "notification.id" for new visitors for versions from 160000.beta4 to 160000. Writes were attempted as "notificationId" in released 160000 however they may have failed if the visitor was new when those releases were in the wild. However those new on 160000.beta4 to 160000.beta8 will have records saved as "notification.id" that will be converted here.

See related tickets below for more details on the history of the issue.

Validation

Tests

Info

Checklist

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

Programming Checklist
Interfaces:

• Don't use default export
• New interfaces are in model files

Functions:

• Don't use default export
• All function signatures have return types
• Helpers should not access any data but rather be given the data to operate on.

Typescript:

• No Typescript warnings
• Avoid silencing null/undefined warnings with the exclamation point

Other:

• Iteration: refrain from using elem of array syntax. Prefer forEach or use map
• Avoid using global OneSignal accessor for context if possible. Instead, we can pass it to function/constructor so that we don't call OneSignal.context

Screenshots

Info

Checklist

• I have included screenshots/recordings of the intended results or explained why they are not needed

---

Related Tickets

• PR User model/notification events #1028 - Introduced a keyPath from "notificationId" -> "notification.id" without a migration which created this issue:
  • https://github.com/OneSignal/OneSignal-Website-SDK/pull/1028/files#diff-dd2c30ab15a2323012089532df9ab057c1861af04fa6022f1af434781885d39bL114
• [User Model] Fix notification event types; click, willDisplay, and dismiss  #1078 - Changed back to "notificationId" for reads / writes but also did not address the keyPath schema issue.

---

---

This change is