[KennyYe]

Summary

Parity with @tapapplink/react-native 0.3.3. Apps that link the billing user id from several places could fire /ingestIdentify multiple times per launch because setAppUserId always POSTed. 0.3.3 skips when the id matches the last successfully identified value (persisted like trackInstall), coalesces concurrent identical calls into one in-flight request, and still posts when the id changes.

Changes

• Persist successful appUserId in install state; hydrate restores it
• Skip /ingestIdentify when appUserId equals the last successful identify
• Coalesce concurrent identical setAppUserId calls into one POST
• A different appUserId still posts
• Add typed TapAppLinkRedeemResult with optional codeMatches and offer.creatorName
• Bump SDK_VERSION / package to 0.3.3 with changelog

Test plan

• Same id twice in one session posts once and returns skipped
• Cold start with persisted id skips POST
• Concurrent identical calls share one in-flight result
• Different id posts again
• Failed identify is not persisted and retries
• Local ./gradlew test ktlintCheck green
• CI green

After merge: tag v0.3.3 on the merge commit to trigger release.yml (GitHub Release + JitPack).