feat: [SDK-4775] add location opt-out support

[fadi-george]

Description

One Line Summary

Adds an MSBuild-controlled way to exclude the native OneSignal location module and includes a no-location MAUI demo.

Expect in Console.app:

Expect in ADB/LogCat:

Demo app:

Details

Motivation

Apps that do not use OneSignal location features should be able to omit native location dependencies while keeping notification, user, IAM, outcome, and live activity behavior available.

Scope

This introduces <OneSignalDisableLocation>true</OneSignalDisableLocation> for source/package builds, conditionally excludes iOS and Android location native assets, and makes location API calls gracefully no-op when the native module is absent. It also adds examples/demo-no-location with APNs capability and updates demo scripts/styles shared by the examples.

Testing

Unit testing

No unit tests were added; this change primarily affects MSBuild item inclusion and native app packaging paths.

Manual testing

From examples/demo-no-location:

• Android: Ran ./run-android.sh on an emulator, tapped TEST LOCATION REQUEST, and confirmed in Logcat that the location module was excluded (missing-module error, no location dependency linked).
• iOS: Ran ./run-ios.sh on a simulator, tapped TEST LOCATION REQUEST, and confirmed in Console that the location module was missing (missing-module error, no OneSignalLocation.framework in 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
• 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

Made with Cursor

[abdulraqeeb33]

One thing I'd flag before merge: on iOS the missing-module diagnostic uses System.Diagnostics.Debug.WriteLine, which gets compiled out in Release builds. So the log line you relied on during manual testing won't actually show up in a production build — and that's a bit ironic since the whole point here is to leave a breadcrumb when someone calls a location API without the module.

Android is fine since Android.Util.Log.Error always logs, which is really the inconsistency: same situation, two different logging behaviors.

Suggest switching iOS to Console.WriteLine/NSLog, or ideally routing both platforms through the SDK's own OneSignalSDK.DotNet.Core.Debug logging so the message respects the configured log level and shows up consistently.

(Smaller, related: the catch (Exception) is broad enough that a genuine error with the module present would also get logged as "module not available" — might be worth narrowing or softening that wording.)