[KennyYe]

Summary

Bring the Flutter SDK to parity with @tapapplink/react-native 0.3.3 (tapapplink/tapapplink-react-native#6). Apps that link the billing user id from several places could fire /ingestIdentify multiple times per launch. 0.3.3 skips when the id matches the last successfully identified value (persisted like trackInstall), coalesces concurrent identical calls into one request, and still posts when the id changes.

Also expose optional codeMatches and offer.creatorName on typed TapAppLinkRedeemResult from applyCode, matching server redeemCode when already attributed (tapapplink/tapapplink#60).

Changes

• Persist successful appUserId after /ingestIdentify; 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; failed identify is not persisted and retries
• Add typed TapAppLinkRedeemResult / TapAppLinkRedeemOffer with nullable codeMatches and offer.creatorName
• Bump package / sdkVersion to 0.3.3 with changelog (en-AU)

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 future
• Different id posts again
• Failed identify is not persisted and retries
• applyCode success exposes codeMatches and nullable offer.creatorName
• CI green

After merge: tag v0.3.3 on the merge commit to trigger publish.yml pub.dev publish.