feat(ui): add native github-flavored markdown tables with typography styling

[jospaquim]

This PR significantly enhances the Markdown rendering capabilities of ByteStash by introducing native support for GitHub-Flavored Markdown (GFM) tables and fixing layout breaking issues caused by plain text/ASCII tables.

Changes Made

• Native GFM Tables: Integrated remark-gfm into the React MarkdownRenderer component allowing standard Markdown tables to be parsed into actual HTML table elements.
• Typography Auto-Styling: Added the official @tailwindcss/typography plugin to the Tailwind configuration. This automatically applies beautiful, cohesive styles (borders, alternating rows, paddings) to the newly rendered Markdown tables through the .prose class wrapper.
• ASCII Tables Layout Fix: Removed the destructive word-break: break-all behavior from FullCodeBlock and PreviewCodeBlock. Replaced it with native horizontal scrolling (overflow-x: auto), which prevents long lines of code, logs, and wide ASCII text-tables from breaking their structural shape when reaching the container's edge.

Testing Instructions

1. Open or create a Code Snippet and set its language to "Markdown".
2. Paste a standard GFM table (| Header | Header |) and save.
3. Open the "Full View" and verify the table renders natively with Tailwind typography styles.
4. Paste a wide line of un-wrapped plain text or an ASCII design and verify that a horizontal scrollbar appears, strictly preserving the text format without line-breaks.

Type of Change

• New feature (non-breaking change which adds functionality)
• Bug fix (Fixed text breaking behavior for pre-formatted blocks)

[jordan-dalby]

Very nice! Would you mind rebasing this branch with the current version of main, I merged your other PR separately. Thanks! :)

[jospaquim]

All set! I've rebased the branch with the current main as requested. Let me know if you need anything else. @jordan-dalby

[jordan-dalby]

All set! I've rebased the branch with the current main as requested. Let me know if you need anything else. @jordan-dalby

Hi! I think you kept the wrong commit, this commit is from the previous PR.

[jospaquim]

You're right, thanks for catching that. I've removed the unrelated commit and updated the PR.