feat(replay): raise native floors for session replay v2 trigger groups

[marc-merino]

Knit Bundle

View bundle

This PR is part of Knit bundle session-replay-v2-trigger-groups-on-mobile.

See the other review objects in this bundle:

• posthog-ios: feat(replay): support session replay v2 trigger groups posthog-ios#921
• posthog-android: feat(replay): support session replay v2 trigger groups posthog-android#850
• posthog-flutter: feat(replay): raise native floors for session replay v2 trigger groups #648 (this PR)
• posthog-js: feat(react-native): support session replay v2 trigger groups posthog-js#5239

Bundle id: session-replay-v2-trigger-groups-on-mobile
Bundle title: Session replay v2 trigger groups on mobile

One of four PRs adding session replay v2 trigger groups to the mobile SDKs (Android, iOS, React Native, Flutter). You can see the unified description of the whole change here: Svartal bundle. The four PRs are linked above.

💡 Motivation and Context

Closes #545.

Flutter session replay runs on the native SDKs: Dart captures go through the native capture pipeline, and posthog-android / posthog-ios fetch the remote config and decide whether to record. So once the native SDKs evaluate v2 trigger groups, Flutter apps get them without Dart changes. This PR only raises the native floors to the releases that will contain that support:

• posthog-android [3.73.0,4.0.0)
• posthog-ios >= 3.91.0 (podspec and Package.swift)

Merge order: this can only merge after the Android and iOS PRs (linked in the Knit block above) are released. Until then the Android and iOS builds here can't resolve those versions, so CI is expected to fail. If the native releases ship under different version numbers, I'll update the floors. The example apps' Package.resolved files are left as they are until the iOS release exists.

💚 How did you test it?

There is no Dart or plugin code change. The trigger-group behaviour itself is tested in the native PRs: unit tests, plus end-to-end runs of the Android sample and the iOS example app against a mock server. Once the native releases exist I'll run the Flutter example on Android and iOS against the same mock and post the results here.

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

If releasing new changes

• Ran pnpm changeset to generate a changeset file

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

• Driven by me in Ivaldi, my agent workspace, with Claude Code (Opus 5.5). Same approach as feat(replay): forward throttleDelay to native and raise floors for replay debug properties #597: raise the floors once native supports the feature.
• The feature spans four repos, so I ran it as one Knit bundle: the Android, iOS, React Native and Flutter changes were built, tested and versioned together. All four diffs side by side on Svartal.