[Fix] OneSignalConfig.androidlib version numbers in build.gradle

[shepherd-l]

Description

One Line Summary

Sets version numbers in the OneSignalConfig.androidlib build.gradle to match the versions specified in Unity

Details

Motivation

Fixes #670 READ_PHONE_STATE permission being added to Android builds
Fixes lower build-tools versions being needed for Android builds than the version the Unity Editor comes with

• I was able to reproduce a licensing 30.0.3 build-tools build error in a new project with the OneSignal SDK on Unity 2022.3.14 which comes with build-tools 32.0.0. The lower build-tools error version may differ depending on the Unity Editor version.

Not specifying a version number in the build.gradle sets it to a low version instead. minSDKVersion was set to 1 and added the READ_PHONE_STATE permission. Lower build-tools versions than the one the Unity Editor comes with were being required when building for Android. compileSDKVersion and targetSDKVersion have also been changed to match the versions specified in Unity

Scope

OneSignalConfig.androidlib has changed and devs need to regenerate it to apply the changes.
To apply the fix devs need to:

1. Delete their OneSignalConfig.androidlib
2. Go to Window > OneSignal SDK Setup and run the "Copy Android plugin to Assets" step

Testing

Manual testing

Tested OneSignal initialization, app build with Unity 2021.3.10f1 of the OneSignal example app on a emulated Pixel 4 with Android 12.

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