fix(chat): stop gating the remove badge on a variant that cannot express it

hover-hover expands to '@media (hover:hover) and (pointer:fine) { &:hover }',
so it binds to the element carrying the class. On the badge that meant every
rule required hovering the badge itself, making the whole chain dead CSS —
the badge was simply always visible.

Rather than rebuild the gating, drop it: an always-visible control is
reachable on touch and stays visible while holding keyboard focus, which the
reveal-on-hover form could not manage without special cases for both.

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/home/components/user-input/components/attached-files-list/attached-files-list.test.tsx

@@ -73,14 +73,14 @@ describe('AttachedFilesList', () => {
     expect(wrapper?.className).toMatch(/max-w-/)
   })
 
-  it('reveals the remove control on keyboard focus, not only on hover', () => {
+  it('keeps the remove control visible rather than gating it on hover', () => {
     render([file({})])
 
+    // A reveal-on-hover badge is unreachable on touch and invisible while it holds
+    // keyboard focus, so it must not be opacity-gated at all.
     const remove = container.querySelector('button[aria-label^="Remove"]')
-    // Hidden only where a pointer can reveal it, and focus has to reveal it there too —
-    // otherwise a keyboard user tabs onto a fully transparent control.
-    expect(remove?.className).toContain('hover-hover:opacity-0')
-    expect(remove?.className).toContain('hover-hover:focus-visible:opacity-100')
+    expect(remove).not.toBeNull()
+    expect(remove?.className).not.toMatch(/opacity-0/)
   })
 
   it('drops the image and reveals the type icon when the preview fails to decode', () => {

apps/sim/app/workspace/[workspaceId]/home/components/user-input/components/attached-files-list/attached-files-list.tsx

@@ -117,10 +117,10 @@ const AttachedFileChip = React.memo(function AttachedFileChip({
             onRemoveFile(file.id)
           }}
           aria-label={`Remove ${file.name}`}
-          /* Visible by default so a coarse pointer never has to discover it through an
-             emulated hover; fine pointers get reveal-on-hover, plus reveal-on-focus so
-             it is never transparent while it holds the keyboard focus. */
-          className='absolute top-[2px] right-[2px] flex size-[16px] items-center justify-center rounded-full border border-[var(--border)] bg-[var(--surface-2)] text-[var(--text-body)] transition-opacity hover-hover:opacity-0 hover-hover:focus-visible:opacity-100 hover-hover:group-hover:opacity-100'
+          /* Always visible: reveal-on-hover would hide it from touch and from keyboard
+             focus, and `hover-hover` cannot express "while the chip is hovered" from
+             here anyway — it carries its own `&:hover`, so it binds to this element. */
+          className='absolute top-[2px] right-[2px] flex size-[16px] items-center justify-center rounded-full border border-[var(--border)] bg-[var(--surface-2)] text-[var(--text-body)]'
         >
           <X className='size-[10px]' />
         </button>