CKEditor 5 PoC

• Setup a "new-blog-editor" feature flag
• Allow loading of old blogs using the old components
• Install CKEditor 5 and use the inline mode to make it resemble our existing medium-editor as much as possible
• Install the CKeditor 5 plugins that allows conversion of markdown into our medium html
• Limit the styles and functionality as much as possible. We want to create a bloat-free experience with minimum toolbars and chrome that fits into the overall site.
• Users should only be to chose from predetermined styles.
• Make sure we provide the ability to quickly create bulleted lists and numeric lists
• Make sure we can easily copy text from wordpress sites and other rich copy sources
• New blogs should be tagged with an attribute that marks them as "version2"
• New blogs should load in the new editor
• Old blogs should load in the old editor
• Make sure we can save on the backend

We're going to roll this out as a POC behind a feature flag

We'll create a card to stand up a built package repo for a blog editor with all our plugins packaged and minified

If the v1 blogs can be displayed and saved with the new editor, we can just turn it on with the FF

If we can't successfully redisplay working blogs, we'll tag the new blogs with v2 on the backend

We need to change this MR to point to an epic branch: epic/blogs-34 and get this merged in so we can start iterating on the look and feel and build / bundle next sprint