Change accepted syntax for code fence

[BartoszGrajdek]

We're currently working on adding styles to code fence & inline code blocks to Live Markdown. After some discussion regarding code fence/pre block we agreed that the best way to handle it is to limit the accepted syntax variations.

This PR adds these changes directly to ExpensiMark 🙌🏻

Fixed Issues

$ GH_LINK

Tests

1. What unit/integration tests cover your change? What autoQA tests cover your change?
   All of the tests that have changed in this PR
2. What tests did you perform that validates your changed worked?
   I tested it both in Live Markdown & in the Expensify App to make sure that it didn't break anything

QA

1. What does QA need to do to validate your changes?
   Check if there's just one syntax valid for pre blocks which should be:

(triple backticks)
Content...
(triple backticks)

3. What areas to they need to test for regressions?
   Mainly Expensify chat & how it treats messages sent with different syntax variations. Live Markdown will include these changes after we get this PR merged 👀

Screen.Recording.2024-05-14.at.14.18.30.mov

[dangrous]

Cool, this looks good and makes sense as a simplification. Do you mind sharing the discussion (was it an issue? Slack?) that led to this just so I can read that before merging? Thank you!

[BartoszGrajdek]

The link to a slack thread is in the PR description, let me know if you have access to it 😄

[dangrous]

So I think that link goes to the SWM slack and I can't access. Basically I just wanted to make sure this was run by someone on the Expensify side before I merged? Since it's (sort of) a product decision. I think this makes the most sense to me but wanted to make sure I was the second opinion haha. Thank you!

[BartoszGrajdek]

Hi, sorry - I was on sick leave last week 😅

I've sent you screenshots of our discussion with Expensify on Slack in a DM 🙌🏻

[dangrous]

Thank you! That was helpful - merging now.

[dangrous]

(and glad you're feeling better!)