Prevent italic or strikethrough emojis on Android

[Skalakid]

Details

This PR fixes adding italics and strikethrough style to the emojis on Android and web platforms

Related Issues

Expensify/App#14676

Manual Tests

1. To the text that contains emojis, add italics styling, e.g. _🥰 test 😇 test 🥹_
2. Verify if the text has italics style and emojis don't
3. Verify if it still works when adding other styles around it, e.g. # *~_🥰 test 😇 test 🥹_~*
4. Verify if emojis aren't strikethrough
5. Test it with different style combinations

Linked PRs

[tomekzaw]

Left some suggestions in the comments, also a unit test suite would be much appreciated.

[tomekzaw]

Also, please provide some unit tests in Java to verify the implementation.

[289Adam289]

I've tested this pr on very example app platform and E/App platforms and I could not find anything. Everything works well including preventing formatting on emojis.

[tomekzaw]

Suggested change

	import org.json.JSONException;
	import org.json.JSONObject;

[tomekzaw]

Just FYI, I also needed class MarkdownRange so I added it in #559. I hope you can reuse mine in this PR.

[Skalakid]

Done in 692de7c

[tomekzaw]

Please wrap beginSection/endSection calls with try/finally block

[tomekzaw]

Shouldn't this check be symmetric? So it covers both _text😀_ and _😀text_?

Also, let's rename newRange and currentRange to leftRange and rightRange.

Let's avoid creating newRange object at all if possible, i.e. move the constructor call into the conditional.

[Skalakid]

We decided to close this PR and rewrite the solution to TypeScript at #591. After the discussion, we agreed that after enabling custom parsers in the live markdown library, it would be better not to interfere with their results. Because of that, we moved the range splitting algorithm to the parseExpensiMark so all platforms get the split ranges. It also gives a choice in custom parser implementation if someone wants to remove styles from emojis