chore: Identify API for MAUI refactor

[abelonogov-ld]

Make architecture more iOS standard ( delegate )

---

Note

Medium Risk
Refactors the identify hook/bridge path to call into SessionReplayService via a new delegate method, which could affect when/if identify events are emitted. Risk is limited to session-replay observability behavior (no auth/payment changes) but touches cross-platform bridge code.

Overview
Refactors Session Replay’s identify handling so both the native SDK hook and the MAUI/C# bridge proxy delegate directly to SessionReplayService.afterIdentify(...), instead of constructing identify payloads inside SessionReplayHook/SessionReplayHookProxy.

LDReplay.hookProxy is now a computed property derived from the current client, and SessionReplay reuses a single SessionReplayHook instance with a weak delegate. SessionReplayService now retains observabilityContext and owns the identify payload creation/scheduling.

Minor updates include conditional Common imports for non-CocoaPods builds, a formatting fix in InitializeSessionOperation, and enabling crashReporting in the test app’s Observability plugin options.

^{Written by Cursor Bugbot for commit 01a088d. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Computed hookProxy creates new instance on every access

Medium Severity

The hookProxy property changed from a stored property to a computed property, meaning every access allocates a new SessionReplayHookProxy (an NSObject subclass) instead of returning a cached instance. This is particularly wasteful for the C#/MAUI bridge, where each call like LDReplay.shared.hookProxy?.afterIdentify(...) creates a throwaway object. The sibling LDObserve.shared.hookProxy remains a stored property set once in getHooks(), making this inconsistent across the two plugins.