fix: Ensure that notifications on legacy http integrations navigate to the origin

[itrush]

Ensure that notifications on legacy http integrations navigate to the origin

Details

There was an issue with legacy HTTP integrations where the defaultNotificationUrl was never saved in the DB. As the result if a notification was sent without explicit launch url, the service worker logic would default to the worker's scope which is in the os.tc domain. This in turn would redirect users to OneSignal dashboard rather than to the customer's site.

To account for missing default notification url, we try to get the default URL from the app config on notification click and save it to the DB for the future use. Choosing between notification received and clicked to add this logic, decided on notification clicked to avoid doing extra api call when the user may never click the notification.

Verified in Chrome, Firefox and Safari that when clicking on a notification it redirects to the origin instead of the os.tc domain.

Note: will only merge it after Thanksgiving

Systems Affected

• WebSDK
• Backend
• Dashboard

Validation

Tests

There seem to be no tests for the service worker flows so didn't add any new ones 🤔 Did an extensive manual test in Chrome, Safari and Firefox.

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

http.notification.click.fix.mov

Checklist

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

---

Related Tickets

https://app.asana.com/1/780103692902078/project/1211950939908862/task/1210115044974433?focus=true

---

---

This change is 

[jkasten2]

Logic looks good to me, just one comment on types.

[fadi-george]

Changes look good, I'll test it some more.

[fadi-george]

Verified original issue and fix though had to use something like proxyman to give it my local built service worker.