feat: [SDK-4768] support disabling location module

[fadi-george]

Description

One Line Summary

Adds ONESIGNAL_DISABLE_LOCATION support so Capacitor apps can exclude the native OneSignal location module from Android and iOS builds.

Details

Motivation

Apps that do not use OneSignal.Location should be able to remove the native location module, matching the Flutter SDK behavior and reducing unnecessary native dependency surface.

Scope

This PR updates Android Gradle, CocoaPods, and SwiftPM dependency resolution to omit location when ONESIGNAL_DISABLE_LOCATION=true or 1 is set. It keeps the JavaScript API stable and makes Android location bridge calls no-op safely when the location module is missing.

Testing

Unit testing

Existing TypeScript bridge tests were run; no new unit tests were added because the public TypeScript API is unchanged and the behavior is native dependency-resolution/runtime fallback logic.

Manual testing

• bun run lint
• bun run test
• bun run build
• ONESIGNAL_DISABLE_LOCATION=true Android dependency resolution confirmed modular core, notifications, and in-app-messages artifacts
• ONESIGNAL_DISABLE_LOCATION=true ./gradlew :onesignal-capacitor-plugin:compileDebugKotlin
• ONESIGNAL_DISABLE_LOCATION=true swift package describe --type json confirmed OneSignalLocation is omitted
• ONESIGNAL_DISABLE_LOCATION=true pod ipc spec OneSignalCapacitorPlugin.podspec confirmed location-free CocoaPods subspecs

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

[sherwinski]

@claude review

[sherwinski]

@claude review once

[sherwinski]

If the scope is cancelled while OneSignal.Location.requestPermission() is suspended, the new catch (t: Throwable):

• catches the CancellationException instead of letting cancellation propagate,
• logs a misleading "location module is not available" error,
• then calls call.resolve() on the destroyed bridge — the exact crash path the previous fix removed.

Fix: rethrow cancellation before the broad catch:

try {
    OneSignal.Location.requestPermission()
} catch (e: CancellationException) {
    throw e
} catch (t: Throwable) {
    logLocationModuleNotAvailable(t)
}

[sherwinski]

Each try/catch in this file also throws when the SDK isn't initialized yet, which can be confusing to debug. Consider a message like "OneSignal.Location call failed — the location module may not be included in this build" or detecting the module-missing case specifically.