feat(markdown): use new markdown crate

[sdwoodbury]

What this PR does 📖

• uses the markdowns crate, produced by Satellite.im.
• Transforms ascii emojis to unicode ex: :O -> 😮
• detects messages that consist of only emojis and whitespace and enlarges them
• makes markdown support configurable in settings
• doesn't support lists yet
• adds css for markdown relates classes, fixing the markdown bugs present in dev. (the markdown crate isn't technically needed to do this but the two have been tested together).

Which issue(s) this PR fixes 🔨

• Resolve bug(markdown): markdown never worked #1305

Special notes for reviewers 🗒️

Additional comments 🎤

[phillsatellite]

Hey Stu I found a couple things while testing with the most latest commit (Verified that the commit Im on has the reply fix that you just recently added in) These are able to be replicated on all OS's

• It doesnt seem like all the markdowns show up in replies, Bold appeared fine for me but all the other markdowns wouldnt appear

Screen.Recording.2023-10-17.at.12.43.59.PM.mov

• Not all markdowns are appearing in the sidebar, bold appears fine but none of the others will appear

• Markdowns arent appearing in Pinned messages

• I also couldn't get underline markdowns to work

• I used the code markdown and put "cargo run --release" in there and you can see in screenshot it just says "run --release"

[sdwoodbury]

@phillsatellite underline isn't supported.

[stavares843]

is there specific ascii that are allowed? some didnt converted into emoji, example the : P one

[luisecm]

Looks like the existing markdown to send code in a message is not working with this PR and thats why the chats tests are failing

[sdwoodbury]

is there specific ascii that are allowed? some didnt converted into emoji, example the : P one

yes. i think i'll move that code into uplink instead of the crate. that way it will be more clear to us. as for the above list, it's too much. don't care about most of those. :P will be added.

[sdwoodbury]

I found that code blocks don't display html tags - probably because messages are displayed using dangerous_html. needs some more thought.