Wait for user to provide consent before executing operations

[fadi-george]

Description

1 Line Summary

Addresses: https://app.asana.com/1/780103692902078/project/1198177413178126/task/1211152956512052?focus=true

• move consent logic out of login operation executor and move it to operation repo

Details

Current erorr:

• Currently if the developer sets consent required to true but user never gives consent. The display notification is still shown (but subscription is never created. Additionally the Login Operation executor throws an error.

Changes:

• Updates default test context to not have prompts manager autoprompt to not trigger operations like login
• Adds new isConsentRequiredButNotGiven helper to check against consent required and consent given flags.
• Adds new prop OneSignal._consentGiven which is loaded in init . This is needed since we dont we to add delay for the login call and don want to make actions like addTags async.
• Removes 'consentGiven' from db schema as this was a typo when it shouldve been 'userConsent'
• Add isConsentRequiredButNotGiven checks to addTag, addTags, addEmail, addSms, etc.
• Adds user config check requiresUserPrivacyConsent to getConsentRequired call.

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 

[sherwinski]

just double checking that we don't use this anywhere?

[sherwinski]

I assume we replaced it with crypto.randomUUID()?

[fadi-george]

Yes we use crypto.