fix: robustify interop of exports and props

[dummdidumm]

• don't throw a dev time error when binding to an export (fixes false positive bind error  #11008)
• remove bindings that are for component exports (this also includes when you pass a regular property; we could try to check if there's a setter to keep normal props with the same name as exports, but I doubt it matters in practise)
• throw an error when using a component export with the same name as a property

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: a36973d

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

[Rich-Harris]

should this be considered a breaking change?

Suggested change

	fix: robustify interop of exports and props
	breaking: robustify interop of exports and props

[dummdidumm]

Mhm true - in runes mode at least this is a breaking change, so I should also note that in the docs

[Rich-Harris]

LGTM aside from the question about the changeset

[trueadm]

There appears to be some TS issues with the docs that is causing the CI to fail on the svelte-5-preview build.