fix: correctly validate undefined snippet params with default value

[paoloricciuti]

Closes #15749

Technically we could've avoid all the fallback_idx conundrum and just allow undefined too but this should be more correct most of the times and it's not really a problem since it's mostly in dev. I also thought of using a Set instead of an array but it's not really worth it since there will never be a lot of params anyway.

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.
• If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

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

[changeset-bot]

🦋 Changeset detected

Latest commit: da36864

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

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@15750

[Rich-Harris]

we can simplify this by just using arguments — will push a change

[paoloricciuti]

Uh that's frickin smart