fix: make $props() rune non-generic

[Rich-Harris]

The $props() rune should not accept a type argument. Instead, component authors should type their props like any other variable declaration:

-let { message } = $props<{ message: string }>();
+let { message }: { message: string } = $props();

Otherwise, things can break because you're relying on inference:

In the above image you can see that the type is widened from string to string | number because when using the generics notation, TypeScript takes the initializer into account when generating the type - which is not what we want.

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests and linting

• Run the tests with pnpm test and lint the project with pnpm lint

[changeset-bot]

🦋 Changeset detected

Latest commit: c19754c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[dummdidumm]

Let me quickly test if language-tools also support the non-generic notation

[jgb-solutions]

Damn I'll need to update my code again. LOL!

[merisbahti]

Is this a reasonable regex (with replace) to do the migration?

I'm using vscodes find/replace function, the search regex is: = \$props<(.*)>\(\) and the replace is: : $1 = $props()

Before

#After

[dummdidumm]

Yeah that looks sensible