Inconsistent HTML escaping in web and mobile

Description:

When submitting messages that contain Markdown syntax and HTML special symbols via incoming webhooks, the message formatting behavior seems inconsistent between the web and mobile apps. Example payload:

{
  "attachments": [
    {
      "fields": [
				{
				"title":"Title Goes Here",
				"value":"a>b `a>b`"
				}
			]
    }
  ]
}

In the web app, this gets rendered as:

In the mobile app:

On web, the right angle bracket inside backticks gets rendered replaced with >. On mobile, it is shown as-is.

Steps to reproduce:

1. Create an incoming webhook
2. Submit the above payload to the webhook
3. Observe the results

Expected behavior:

The web and mobile apps should behave the same. The behavior (Precisely what markdown syntax in which fields is supported. Precisely what HTML syntax in which fields is supported. What is the escaping logic for unsupported syntax) should be documented.

Actual behavior:

In the web app, this gets rendered as:

In the mobile app:

Server Setup Information:

• Version of Rocket.Chat Server: tested with the SaaS versions of Rocket.Chat, running 6.2.2

Client Setup Information

• Desktop App or Browser Version: tested with the SaaS versions of Rocket.Chat, running 6.2.2
• Mobile App: installed from Google Play, v4.38.0

Start by reproducing the provided incoming webhook payload and compare its rendering in the web and mobile apps, focusing on Markdown and HTML escaping. Done means both clients render the example consistently, with the supported Markdown and HTML behavior and escaping rules documented.