fix: expose default native handlers

[isekovanic]

🎯 Goal

This PR addresses this GH issue.

While exposing a prop might be slightly more convenient, our native handlers have a ton of arguments we don't want to expose every single one of them separately as it will cause an argument storm.

Instead, we expose the default native handlers and allow integrators to use them as they see fit.

For example, they could invoke them with different properties, make them conditionally depend on configuration and similar.

It would also make it easier to conditionally override the handlers in certain scenarios.

Runtime passing of different arguments should still be done on the callsites themselves, this approach is more of a global switch to something else if necessary.

🛠 Implementation details

🎨 UI Changes

iOS

Before	After

Android

Before	After

🧪 Testing

☑️ Checklist

• I have signed the Stream CLA (required)
• PR targets the develop branch
• Documentation is updated
• New code is tested in main example apps, including all possible scenarios
  • SampleApp iOS and Android
  • Expo iOS and Android

[Stream-SDK-Bot]

SDK Size

title	develop	branch	diff	status
js_bundle_size	1975 KB	1975 KB	0 B	🟢