fix: properly resolve sendMessage during memoization

[isekovanic]

🎯 Goal

We have an issue with memoization where if you do the following:

• Override doSendMessageRequest on the Channel level
• Make doSendMessageRequest depend on some local state that gets updated later

only the initial value of that state would be memoized.

Zendesk ticket: https://getstream.zendesk.com/agent/tickets/55303

🛠 Implementation details

The reason why we wrap sendMessage in a ref is due to the fact that simply adding it to the dependency array will likely cause a ton of rerenders of components everywhere. I realise it's a hacky way to solve this, but more conventional methods such as wrapping it inside a useCallback are a bit difficult since we would need to wrap all of its other dependencies in callbacks as well, causing a cascading effect. Ideally, this should be solved by getting rid of the useMemo entirely in the MessageInputContext, but for now this'll have to do.

🎨 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	442.099609375 KB	442 KB	0 B	🟢

[stream-ci-bot]

:tada: This PR is included in version 5.38.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: