test(rich-markdown-editor): scope paste tests to what MarkdownPaste actually gates

Inline-only marks (single-asterisk italic, ~~, single-backtick code) are intentionally not detected
by looksLikeMarkdown (single `*` would false-positive on e.g. `*args`); they route through the
Markdown extension's own paste path, not MarkdownPaste. Move them from the rich-render cases to the
defers-to-default cases so the suite tests the handler it names.

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/files/components/file-viewer/rich-markdown-editor/markdown-paste.test.ts

@@ -104,17 +104,21 @@ describe('markdown paste', () => {
     ['empty string', ''],
     ['whitespace only', '   \n\n  '],
     ['a bare thematic break (ambiguous — needs another markdown signal)', '---'],
+    ['inline-only italic (single asterisk would false-positive on e.g. *args)', 'an *italic* word'],
+    ['inline-only strikethrough', 'a ~~struck~~ word'],
+    ['inline-only code', 'some `code` here'],
   ])('leaves %s to the default handler', (_label, text) => {
     editor = mount()
     expect(paste(editor, text)).toBe(false)
   })
 
+  // Only structural / unambiguous constructs gate the markdown parse. Inline-only marks that
+  // `looksLikeMarkdown` deliberately omits to avoid false positives — single-asterisk italic
+  // (`*args`), `~~`, single-backtick code — are covered by the Markdown extension's own paste path,
+  // not MarkdownPaste, so they belong to a different test surface.
   it.each([
     ['heading', '# Heading', 'heading'],
     ['bold', 'a **bold** word', 'bold'],
-    ['italic', 'an *italic* word', 'italic'],
-    ['strikethrough', 'a ~~struck~~ word', 'strike'],
-    ['inline code', 'some `code` here', 'code'],
     ['bullet list', '- one\n- two', 'bulletList'],
     ['ordered list', '1. one\n2. two', 'orderedList'],
     ['task list', '- [x] done\n- [ ] todo', 'taskList'],