fix(interfaces): unbreak the build and guard the chat attachment read

- data-table.tsx kept a './document-table.css' import after being moved into
  its own directory; the CSS sits one level up, where both siblings correctly
  reference it as '../'. tsc does not resolve CSS imports and vitest stubs
  them, so this only surfaced in a real Next build — CI was red. Swept every
  relative asset import repo-wide; this was the only broken one.

- The chat module read attachments outside its try. toChatFilePayloads rejects
  when FileReader errors (a file deleted or moved between selection and send),
  and by that point the turn is committed: runningRef is set and a streaming
  bubble is on screen. An escaping rejection left the bubble spinning and the
  guard stuck true, so every later send returned early and the module stayed
  dead until remount. The existing finally already tears this down correctly;
  the read just needed to be inside it.

Author: waleedlatif1

apps/sim/components/resources/file-view/components/data-table/data-table.tsx

@@ -2,7 +2,7 @@
 
 import { forwardRef, memo, useCallback, useImperativeHandle, useRef, useState } from 'react'
 import { cn } from '@sim/emcn'
-import './document-table.css'
+import '../document-table.css'
 
 interface EditConfig {
   onCellChange: (row: number, col: number, value: string) => void

apps/sim/components/resources/interface-view/components/module-renderer/components/chat-module/hooks/use-interface-chat.ts

@@ -359,13 +359,21 @@ export function useInterfaceChat({
         settle(succeeded ? NO_OUTPUT_NOTE : CHAT_ERROR_MESSAGES.GENERIC_ERROR)
       }
 
-      /**
-       * Read here rather than in the composer: only images arrive pre-read, so
-       * every other attachment is turned into its base64 payload at send time.
-       */
-      const filePayloads = await toChatFilePayloads(files)
-
       try {
+        /**
+         * Read here rather than in the composer: only images arrive pre-read, so
+         * every other attachment is turned into its base64 payload at send time.
+         *
+         * Inside the `try` because `FileReader` rejects on an unreadable file —
+         * a real case, since a file can be deleted or moved between selection
+         * and send. By this point the turn is already committed: `runningRef` is
+         * set and a streaming bubble is on screen. Escaping here would leave the
+         * bubble spinning forever and `runningRef` stuck true, so every later
+         * send would return early and the module would be dead until remount.
+         * The `finally` below is the only thing that clears that state.
+         */
+        const filePayloads = await toChatFilePayloads(files)
+
         await execute({
           workflowId: runId,
           endpoint: activeEndpoint,