chore: [SDK-4774] add Unity no-location demo

[fadi-george]

Description

One Line Summary

Adds a runnable Unity demo that validates OneSignal without the native location module.

Details

Motivation

The Unity SDK needs a dedicated example for apps that exclude the native location module, matching the no-location demos in sibling SDKs and giving reviewers/users a concrete validation path for the opt-out plumbing introduced in the parent PR.

Scope

• Adds examples/demo-no-location with its own scene, scripts, project settings, package manifest, and README.
• Exports ONESIGNAL_DISABLE_LOCATION=true from the demo run scripts so CLI builds resolve granular native dependencies.
• Adds Android Gradle templates/proguard rules and iOS build scripting for the no-location dependency set.
• Adds link.xml for IL2CPP managed stripping, .env.example, app ID injection during scripted builds, and a test notification button.
• Updates generated dependency provenance comments to point at the per-project manifest location.

Testing

Unit testing

Not added; this PR is a Unity demo project and build-script addition.

Manual testing

• Verified as part of the original SDK-4774 branch before splitting:
  • examples/demo-no-location/run-ios.sh --no-install generated granular pods without OneSignalLocation.
  • xcodebuild for the no-location iOS simulator build completed with EXIT=0 and no OneSignalLocation.framework linked.
  • examples/demo-no-location/run-android.sh --no-install built the APK with granular Android dependencies (core, notifications, in-app-messages).
  • ./run-all.sh --sdk=unity --platform=ios passed with 34 tests for the main demo path.

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