* Switch to dompurify for sanitizing markdown content
Switches us from using `insane` to instead use `dompurify`, which seems to be better maintained and also has some nice features, such as built-in trusted types support
I've tried to port over our existing sanitizer settings as best as possible, but there's not always a 1:1 mapping between how insane works and how dompurify does. I'd like to get this change in early in the iteration to catch potential regressions
* Remove logging and renaming param
* Move dompurify to browser layer
* Fixing tests and how we check valid attributes
* Allow innerhtml in specific files
* Use isEqualNode instead of checking innerHTML directly
innerHTML can return different results on different browsers. Use `isEqualNode` instead
* Reapply fix for trusted types
* Enable ALLOW_UNKNOWN_PROTOCOLS
I beleive this is required since we allow links to commands and loading images over remote
* in -> of
* Fix check of protocol
* Enable two more safe tags
* Use shared webpack version instead of installing locally for simple-browser
* Use npm for building markdown preview
* render markdown in webview.
* update markdown preview height and offset
* Add basic custom notebook renderer point
* update css
* style update.
* update markdown header padding left
* Add example of loading katex to extend the markdown-it renderer
* Rename global to make clear it only applies to markdown-in
* hide/remove markdown preview
* Add wait for initial markdown preview rendering before showing notebook
* Add double click to switch to editing mode
* Fix markdown cells not getting updated after editing
* style polish
* notebook.experimental.useMarkdownRenderer
* switch render strategy.
* Adding very intial drag drop support for notebook markdown cells
* Implement drag/drop stubs for test classes
* Revert unrelated file changes
* Move markdown notebook math to own extension
* Add missing imports
Co-authored-by: rebornix <penn.lv@gmail.com>
