[Fix] Add OneSignal-Subscription-Id header to create user requests

[shepherd-l]

Description

1 Line Summary

Adds OneSignal-Subscription-Id header to create user requests

Details

• Adds OneSignal-Subscription-Id and refresh_device_metadtat: true header to user create requests
• Adds OneSignal-Subscription-Id header to all user update requests
  • Previously the header was only added to session related requests

Systems Affected

• WebSDK
• Backend
• Dashboard

Validation

Tests

Info

Added unit tests for refresh_device_metadata and OneSignal-Subscription-Id for create user and OneSignal-Subscription-Id for update user.
Manually tested on the OneSignal WebSDK Sandbox: Create user requests from login to an identified user from an identified user (OneSignal-Subscription-Id and refresh_device_metadata sent) and fresh install (no OneSignal-Subscription-Id). Update user requests from adding tags (OneSignal-Subscription-Id sent).

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

---

---

This change is