refactor: add optional max length to parse expensimark

[Uzaifm127]

Details

parseExpensiMark() uses ExpensiMark from expensify-common to convert Markdown into formatted ranges.

This PR makes the parser length configurable while keeping the existing 4,000-character limit as the default by adding an optional argument to parseExpensiMark function. It also updates expensify-common to 2.0.201, which contains the optimized ExpensiMark implementation required by this parser.

Related Issues

Expensify/App#95210

Manual Tests

N/A

Linked PRs

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Uzaifm127]

I have read the CLA Document and I hereby sign the CLA

[Uzaifm127]

@linhvovan29546

Do we need the QA for this PR?

I think we don't need it. We can test this in react-native-live-markdown/example app by modifying the MAX_PARSABLE_LENGTH from code. We can do the QA in version bump PR of Expensify/App repo.

---

@JS00001

Do we need to update the README.md for this change? like the following:

The built-in `parseExpensiMark` parser accepts an optional `maxLength` argument. It defaults to 4,000 characters, so existing callers keep the current bounded behavior. Applications that have a different safe limit can pass that limit explicitly from a worklet parser:

function parser(input: string) {
  'worklet';

  return parseExpensiMark(input, 10000);
}

[linhvovan29546]

Do we need to update the README.md for this change? like the following:

I think we should

[linhvovan29546]

A minor NIT #775 (comment). All good

[Uzaifm127]

Updated the README.md file

[linhvovan29546]

@JS00001 All yours.

[os-botify]

🚀 Published to npm in 0.1.337 🎉

[JS00001]

@Uzaifm127 I think we need one more PR to use the new version, right?

[Uzaifm127]

@JS00001 Yes we need one more App PR in which we will be doing the version bump and passing the MAX_MARKUP_LENGTH as limit to parseExpensiMark function.