Fix Android User calls to always resolve

[nan-li]

Description

One Line Summary

Resolve all Android user namespace methods over the bridge as some were missed.

Details

Motivation

Fixes #799
Fixes #789

Scope

Resolve all User namespace methods over the Android bridge, some of them were missed like addTag or removeTag. This was only for people using await with these methods and waiting on the response, doesn't change any implementation details.

Testing

Unit testing

None

Manual testing

Android Nexus S Emulator API 33, tested with calling addTag with await and seeing that it resolves after these changes.

await OneSignal.User.addTagWithKey("test2", "val2");

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
• 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.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is 

[shepherd-l]

Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @emawby, @jennantilla, @jinliu9508, and @jkasten2)