Added text editor and implemented it in some cases (#122)

[Rahuldeb5]

This doesn't 100% fix #122 but it implements a basic text editor and uses it in the most simplest of cases.

To do:

• Add more features (It just didn't work for me i don't know why; I tried installing more but it just didn't work). So far only works for lists, bold, and italics. Links and colors don't work.
• Add it in more complicated cases like descriptions for meetings

[netlify]

✅ Deploy Preview for stuyepsilon ready!

Name	Link
🔨 Latest commit	254e15a
🔍 Latest deploy log	https://app.netlify.com/sites/stuyepsilon/deploys/66aa55855e1cb1000884e19e
😎 Deploy Preview	https://deploy-preview-181--stuyepsilon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[TheEgghead27]

I am not willing to approve this PR just yet, as there is no back-end sanitization of code (so someone could inject evil scripts in an XSS attack)
Further, we should discuss how to format these HTML contents for our plaintext emails, I see two possibilities

• Keeping our emails plaintext, but extracting the plaintext of the HTML (or using Markdown or some other human-friendly syntax in emails) (I prefer this, because it marginally improves our spam rating, and reduces the odds of email formatting errors)
• Using HTML in our emails (increases complexity and chances of being spam-canned, and would need additional effort to look nice)

[TheEgghead27]

Scary!

[TheEgghead27]

Concerning!

[TheEgghead27]

𝓯𝓻𝓮𝓪𝓴𝔂

[TheEgghead27]

My thoughts: do not implement the text editor for meetings/posts, which are emailed out in plaintext and should remain as such (to reduce complexity), but keep the editor where it is now (organization messages + announcements) where it may be useful to have.

However, before this PR is merged, XSS mitigations must be implemented on the backend for organization messages (announcements are not a likely attack vector because it is only writable by trusted administrators)

[TheEgghead27]

If formatting for meetings/posts are desired, the editor should be adapted to emit Markdown, which will be sent in plaintext verbatim, and parsed to display (with a limited subset of, or no support at all for, embedded HTML)