fix: address Svelte 5 warnings

[metonym]

Fixes #2016.

When using this library with Svelte 5, I'm seeing development warnings in the console.

11:18:07 [vite] ✨ new dependencies optimized: svelte/internal/client
11:18:07 [vite] ✨ optimized dependencies changed. reloading
11:18:07 AM [vite-plugin-svelte] node_modules/carbon-components-svelte/src/Breakpoint/Breakpoint.svelte:43:48 Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update
11:18:08 AM [vite-plugin-svelte] node_modules/carbon-components-svelte/src/OverflowMenu/OverflowMenu.svelte:195:2 The value of 'aria-haspopup' must be exactly one of "false", "true", "menu", "listbox", "tree", "grid" or "dialog"
11:18:08 AM [vite-plugin-svelte] node_modules/carbon-components-svelte/src/TextInput/TextInput.svelte:97:24 Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update
11:18:08 AM [vite-plugin-svelte] node_modules/carbon-components-svelte/src/TextInput/PasswordInput.svelte:91:24 Properties of objects and arrays are not reactive unless in runes mode. Changes to this property will not cause the reactive statement to update

This isn't a blocker, but it'd be nice to address these, especially if it's a backwards-compatible change.

My approach in #2010:

1. Upgrade tooling to Svelte 5 (including upgrading TypeScript).
2. Run svelte-check on source code and/or run npm run build:lib to identify warnings emitted by Svelte 5.
3. Address the warnings until they disappear.
4. Cherry pick c2644a5 and open this PR.

[metonym]

CC @brunnerh – would value any insight/thoughts you might have here. Short term goal is to avoid development warnings if using Svelte 5.

[brunnerh]

The approach seems valid, though all components should also be tested for compatibility. Since the Svelte 5 reactivity system is completely different, there is definitely potential for breakage.

[metonym]

Great, thanks for the review. Keeping track of Svelte 5 compatibility issues in #2012.

[metonym]

Fixed in v0.85.3