Remove ACCESS_COARSE_LOCATION permission

[shepherd-l]

Description

One Line Summary

Removes ACCESS_COARSE_LOCATION from the location module

Details

Motivation

Fixes

• [question]: READ_PHONE_STATE and ACCESS_COARSE_LOCATION permission in final AndroidMatifest OneSignal-Unity-SDK#670
• [Bug]: Use of OneSignal SDK without adding Android and iOS Location Permission OneSignal-Flutter-SDK#803
• and the same in other wrappers

This change was made to avoid the location permission requirement for those who use the com.onesignal:OneSignal package like our wrapper SDKs and do not use location with OneSignal.

Scope

Requires developers to add ACCESS_COARSE_LOCATION to their AndroidManifest themselves if they would like to use OneSignal location. This change reverts back to the player model behaviour.

Testing

Manual testing

Tested calling location request permission with location sharing on, app build with Android Studio 2022.1.1 of the OneSignal example app on an emulated Pixel 4 with Android 12.

Calling OneSignal.Location.requestPermission() without ACCESS_COARSE_LOCATION(or other location permissions) logs and does not crash the app.

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