fix(ios): deliver launch urls, activities and quick actions to scene apps - #11518

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/DevelopmentWorkflow.md#running-unit-tests-application.
• Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/tools/notes/WritingUnitTests.md.

What is the current behavior?

Once an app declares UIApplicationSceneManifest, UIKit stops calling application:openURL:options:, application:continueUserActivity:restorationHandler: and application:performActionForShortcutItem:completionHandler:. The scene delegate bridge covers the warm case by forwarding scene:openURLContexts:, scene:continueUserActivity: and windowScene:performActionForShortcutItem:completionHandler: to those handlers.

When one of these payloads is what launches the app, UIKit delivers it only in scene:willConnectToSession:options:, as connectionOptions.URLContexts, connectionOptions.userActivities or connectionOptions.shortcutItem, and never calls the warm scene callbacks for it. sceneWillConnectToSessionOptions doesn't look at any of them (apart from reading openWindow() data off the first activity), so:

• opening a document from Files / the share sheet, or tapping a custom-scheme or universal link while the app is not running, is dropped
• Handoff / Spotlight continuations that cold-launch the app are dropped
• launching the app from a Home Screen quick action does nothing

There is no sceneOpenURLContexts / sceneContinueUserActivity / scenePerformActionForShortcutItem event, and no call into handlers registered with Application.ios.addDelegateHandler(). The same payloads work when the app is already running, which makes this easy to miss in development.

What is the new behavior?

sceneWillConnectToSessionOptions delivers the launch payloads through the same path as the warm callbacks: it emits the scene event on the window and on Application.ios, then forwards to the legacy delegate handler.

• Delivery happens after the window content is resolved, keeping the pre-scene order where openURL and friends arrived after launch had finished and the root view existed.
• The activity openWindow() attaches to carry window data (<bundleId>.scene) is not forwarded as a continuation (new getLaunchUserActivities helper in scene-delegate-bridge.ts).
• A cold-launch quick action has no completion handler to report to, so oneShotCompletion now accepts undefined.
• The three warm callbacks and the cold-launch path share one helper per payload type, so their events and forwarding can't drift apart.

UIKit sends a given payload either at connect or through the warm callback, never both, so this doesn't double-deliver.

Tests cover the activity filtering and the completion-less oneShotCompletion. The scene delegate itself isn't unit-testable without UIKit, so the cold-launch path was checked by reading the code against the warm callbacks and has not yet been run on a device.