[User Model] Update Privacy Methods

[jennantilla]

Description

One Line Summary

Update Privacy Methods

Details

Motivation

Update & align privacy consent API names across platforms:

• Rename to consentRequired and consentGiven
• Remove public getters for these 2 properties

Scope

Privacy methods can now be invoked with:
window.plugins.OneSignal.setConsentRequired(true);
window.plugins.OneSignal.setConsentGiven(true);

Testing

Unit testing

No Unit Testing was used.

Manual testing

Manual testing with setConsentRequired(true) successfully prevents OneSignal from initializing until setConsentGiven(true) is given. Tested on both iPad running iOS 15.2 and Android Galaxy S21 running Android 13.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is