Type errors on components missing `class` from $$Props interface

[vsergeev]

Describe the bug

Some components, e.g. AccordionItem, Skeleton, ListPlaceholder, and possibly many others, merge $$props.class, but don't expose class in interface $$Props, leading to type errors like:

$ pnpm run check
Error: Object literal may only specify known properties, and '"class"' does not exist in type '{ divClass?: string | undefined; size?: string | number | undefined; }'. (js)
<div class="p-9">
        <Skeleton class="mx-auto" />
</div>
$

Many code examples on https://flowbite-svelte.com/docs/components/skeleton override class.

Components that extend ComponentProps<Frame> aren't affected by this, as they pick up class from Frame props.

Reproduction

<script>
	import { Skeleton } from 'flowbite-svelte';
</script>

<div class="p-9">
	<Skeleton class="mx-auto" />
</div>

$ pnpm run check
...
/home/shinokada/flowbite-svelte-issue-template/src/routes/+page.svelte:6:12
Error: Object literal may only specify known properties, and '"class"' does not exist in type '{ divClass?: string | undefined; size?: string | number | undefined; }'. (js)
<div class="p-9">
        <Skeleton class="mx-auto" />
</div>

====================================
svelte-check found 1 error and 0 warnings in 1 file
$

Flowbite version and System Info

npmPackages:
    @sveltejs/kit: ^2.7.3 => 2.7.3 
    flowbite-svelte: ^0.47.3 => 0.47.3 
    svelte: 5.1.9 => 5.1.9 
    vite: ^5.4.10 => 5.4.10

[shinokada]

v1 fixed this.