fix: regex max stack depth crash

[isekovanic]

🎯 Goal

Fixes the occasional regex maximum depth reached error.

Not going to go into the specifics on why this happens as they're complicated, but I will add a few bullet points:

• Tried porting the latest version of simple-markdown available here, but nothing changed with that and the issue is still noticeable
• The issue typically happens whenever we have one (or more) \n characters, followed by many white spaces; the regex state machine runs something similar to /\s+/g at one point, which considers both. However, despite treating them both as the same character under \s, it actually does a ridiculous amount of backtracking and combinations while all that's going on, even due to a single \n character as it tries to look for every possible scenario.
• Ironically, simply a long sequence of whitespaces finishes in a single go since it manages to match everything in O(n).

Note: We should really look into upgrading our markdown package in general. I was successful in doing so, but decided to separate this fix and the migration since deeper testing would be required.

🛠 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	452 KB	455 KB	+2624 B	🔴