fix: close v1 filter chip when clicking icon

[bdfranck]

Before (the change)

After (the change)

The reason

The problem is a race between Chrome's focus event and the goa-icon shadow DOM re-render:

Step	What happens in Chrome
1	mousedown on goa-icon → browser focuses the parent div
2	focus fires → _focused = true → Svelte re-renders
3	goa-icon receives new theme="filled" prop → shadow DOM re-renders under the cursor
4	mouseup / click fire — but Chrome sees the hit-target changed, so click is dropped

Firefox is more permissive and fires click even when the shadow DOM target shifts mid-gesture, which is why it works there on the first click.

Adding pointer-events: none to .delete-icon makes the goa-icon element transparent to all mouse events, so every click falls straight through to the outer div.chip that holds the on:click={onDelete} handler. The icon in the v1 chip is purely decorative anyway — the whole chip is meant to be the button.

[Copilot]

Pull request overview

Fixes an issue in Chrome where clicking the close icon on the v1 filter chip can fail due to focus-triggered re-rendering of the goa-icon shadow DOM mid-gesture.

Changes:

• Disable pointer event handling on the v1 close icon so pointer events consistently target the chip container click handler.