chore: run addon tests on request

[manuel3108]

The addon tests are the only ones that take quite a lot of time to run. So we run them in a separate runner to get faster general feedback. Additionally most of the changes we do, do not affect the addons itself. In such cases it is wasteful to run the addon tests. Therefore we add a new label needs-addon-integration-tests similar to the needs-platform-tests in kit, that we can add to the prs on a per need basis. Changeset PR's automatically receive that label.

Description

Checklist

• Update snapshots (if applicable)
• Add a changeset (if applicable)
• Allow maintainers to edit this PR
• I care about what I'm doing, no matter the tool I use (Notepad, Sublime, VSCode, AI...)

[pkg-svelte-dev]

Install the latest version of sv from d6218c7:

pnpm add https://pkg.svelte.dev/sv/c/d6218c70252f14c6f727c7d5361f2556b335c373

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/cli/pr/1223

[changeset-bot]

⚠️ No Changeset found

Latest commit: d6218c7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-cli-1223-svelte.vercel.app/

[jycouet]

No luck with the 11 minutes? or?!
In average I think that it's ~7 min the longest... maybe we should just split on more machine but all the time?

I did try https://www.blacksmith.sh/ on a private project and was amazed by the speed gain! should we have an eye on it?

Label can work technically, but is not that practical.