chore: more size reduction

[fadi-george]

Description

1 Line Summary

• more size reduction

// old
 build/releases/OneSignalSDK.page.js
  Size limit: 420 B
  Size:       420 B gzipped
  
  build/releases/OneSignalSDK.page.es6.js
  Size limit: 46.6 kB
  Size:       46.6 kB gzipped
  
  build/releases/OneSignalSDK.sw.js
  Size limit: 13.44 kB
  Size:       13.44 kB gzipped
  
  build/releases/OneSignalSDK.page.styles.css
  Size limit: 8.81 kB
  Size:       8.8 kB  gzipped

// new
  build/releases/OneSignalSDK.page.js
  Size limit: 420 B
  Size:       420 B gzipped
  
  build/releases/OneSignalSDK.page.es6.js
  Size limit: 46.23 kB
  Size:       46.23 kB gzipped
  
  build/releases/OneSignalSDK.sw.js
  Size limit: 13.44 kB
  Size:       13.44 kB gzipped
  
  build/releases/OneSignalSDK.page.styles.css
  Size limit: 8.81 kB
  Size:       8.8 kB  gzipped
  

Details

• more underscore prefix renames of class methods
• change usage of model tag type (string) to ModelChangeTagValue
• remove src/core/objects/PropertiesObject.ts through simple object creation
• simplify ModelChangeTags value from string to number
• simplify DismissPrompt value from string to number
• break up userdirector class into functions
• move getRetryIndicator to loading.ts

Systems Affected

• WebSDK
• Backend
• Dashboard

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

---

---

This change is 

[fadi-george]

moved to user agent detect