refactor(parse and sanitize markdown on server)

[Spencer6497]

This PR shifts the responsibility of parsing and sanitizing markdown from the <RichText/> component to the zod schema definitions via .transform(). To do this, I've added a new buildRichTextValidation zod schema type, and replaced all instances of zod.string() with it, where applicable. Further cleanup PR to come.

• add new parseAndSanitize method, move sanitize to same file
• Create new buildRichTextValidation() zod schema method

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1208848279655976

[Spencer6497]

Tests are failing because at certain points in the CMS, we've nested list items (asterisks in markdown evaluate to <li> tags) inside of Mustache conditional statements. Since the markdown is now getting parsed + sanitized way before stringReplacements are being evaluated, we run into an issue where syntactically important DOM elements (like opening <ul> tags) get trapped inside {{ #conditional }} logic and get deleted when those conditions evaluate to false

[chohner]

Tests are failing because at certain points in the CMS, we've nested list items (asterisks in markdown evaluate to <li> tags) inside of Mustache conditional statements. Since the markdown is now getting parsed + sanitized way before stringReplacements are being evaluated, we run into an issue where syntactically important DOM elements (like opening <ul> tags) get trapped inside {{ #conditional }} logic and get deleted when those conditions evaluate to false

Nice find. Is that a sign of malformed content? I would've hoped that markdown conversion & template replacement to be commutative...

[Spencer6497]

Tests are failing because at certain points in the CMS, we've nested list items (asterisks in markdown evaluate to <li> tags) inside of Mustache conditional statements. Since the markdown is now getting parsed + sanitized way before stringReplacements are being evaluated, we run into an issue where syntactically important DOM elements (like opening <ul> tags) get trapped inside {{ #conditional }} logic and get deleted when those conditions evaluate to false

Nice find. Is that a sign of malformed content? I would've hoped that markdown conversion & template replacement to be commutative...

Nope, unfortunately the content is correct :/ It would be commutative if we were only doing simply text replacements, but since we're executing IF-ELSE logic with conditionals, important HTML gets omitted after it's been parsed/sanitized from markdown

[aaschlote]

can you check if this component renders the RichText with the paragraph with this className?

[Spencer6497]

I added a new test suite, richtest.test.ts, as the rendering is occurring inside of buildRichTextValidation

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
88.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud