Web SDK Refactor: Add ModelStore Class

[fadi-george]

Description

Continuation of the Web SDK Refactor project. This pr is focuses on porting the follow classes/types from the Android SDK: ModelStore , OperationModelStore

Details

• adds ModelStore class
• adds new addAt to ModelStore since cant have overloading for add method
• adds OperationModelStore class but comment out the case options for the create method
• name old Operation to LegacyOperation

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 

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1210104163527286

[sherwinski]

cloned for thread safety

nit: is this still true? I'm not sure if the ported implementation uses anything more complex than async/awaits.

[sherwinski]

nit: Is it possible to use a stronger type here? I guess it would be difficult without refactoring the return type on toJSON