[FIX] Fixes bug in latex-parsing

[c0dzilla]

@RocketChat/core

Closes #9683
Latex rendering function was returning incorrect value leading to resulting message being of the form '=!=<Random.id()>=!='. This pr fixes this.

[engelgabriel]

Testing the PR I had the following result:

But I don't think that latex should be parsed at all inside code formatted boxes or inline code, what do you guys think?

@RocketChat/core ?

[c0dzilla]

@engelgabriel presently latex parsing and markdown parsing callbacks on a message occur independently with latex parsing at higher priority. Latex parsing can be disabled in case inline/block code match occurs. Thoughts?

[nusje2000]

@c0dzilla I think the question should be, what would a user use more often. I think, based on my use case, people use codeblocks more often than latex parsing. Altho latex parsing could be usefull in some cases, I dont think it should be at a higher priority than inline/block code. But that is my opinion

[c0dzilla]

@engelgabriel what is the status on this? Is there anything needed to be done?

[tassoevan]

Thank you for the contribution. However, I'm closing this PR because it collides with other related issues we've worked on, as you can see in #11698 and #11746.