Odd behavior of '>' (greater-than) in Markdown Block

### Impacted plugin

None / Other

### Steps to Reproduce

I wasn't able to replicate this on a private site, but on any given P2 if I add a Markdown block with '>' for quotes or in code blocks(i.e. ```) then save the draft the block alters the '>' and messes up the final rendering.

See demo:
https://d.pr/i/pNg43S

### A clear and concise description of what you expected to happen.

When adding '>', it should not corrupt the Markdown block and should parse it back appropriately instead of replacing it with an HTML entity(as a quote or in a code block as simply '>').

### What actually happened

The '>' got replaced by it's HTML entity equivalent and corrupted the Markdown block.

### Other information

_No response_

### Operating System

macOS

### OS Version

Monterey

### Browser

Firefox

### Browser Version(s)

Version 99

No source files, tests, or entry points are named. Reproduce the issue by saving a Markdown block on a P2 containing greater-than signs in quotes and fenced code, then verify that the characters remain intact and render correctly after saving.

Written by the indexing model from the issue text.