Remove redundant use of coroutineScope inside of LaunchedEffect.

[Sagar0-0]

🎯 Goal

Avoid unnecessary coroutine scope creation inside a LaunchedEffect block and simplify the coroutine launch logic in the PinnedMessagesScreen.

• This improves code readability and adheres to best practices in Compose.
• Avoid manually launching nested coroutines when the outer scope already provides the structured, lifecycle-safe coroutine.
• Creating a CoroutineScope just to immediately launch one job inside another coroutine (LaunchedEffect) is unnecessary indirection and adds no value in our case.
• Keep coroutine usage minimal and clear.

🛠 Implementation details

Replaced the use of rememberCoroutineScope() within LaunchedEffect with a direct suspend call to collect from viewModel.errorEvents. Since LaunchedEffect already provides a lifecycle-aware coroutine scope, creating an additional scope was redundant.

🧪 Testing

This change is covered by existing UI behavior. To verify:

• Trigger a message error in PinnedMessagesScreen.
• Confirm that the Toast still shows the error message correctly.

No additional testing patch is required.

☑️Contributor Checklist

General

• I have signed the Stream CLA (required)
• Assigned a person / code owner group (required)
• Thread with the PR link started in a respective Slack channel (#android-chat-core or #android-chat-ui) (required)
• PR is linked to the GitHub issue it resolves

Code & documentation

• Changelog is updated with client-facing changes
• New code is covered by unit tests
• Comparison screenshots added for visual changes
• Affected documentation updated (KDocs, docusaurus, tutorial)

☑️Reviewer Checklist

• UI Components sample runs & works
• Compose sample runs & works
• UI Changes correct (before & after images)
• Bugs validated (bugfixes)
• New feature tested and works
• Release notes and docs clearly describe changes
• All code we touched has new or updated KDocs

🎉 GIF