chore: update svelte-ecosystem-ci trigger

[dominikg]

compared to vite's trigger, this does not probe pr.pkg.new as we publish all PR commits there anyways.
is this ok or do we have to port that over too?

see https://github.com/vitejs/vite/blob/main/.github/workflows/ecosystem-ci-trigger.yml
and https://github.com/vitejs/vite/blob/38bb268cde15541321f36016e77d61eecb707298/.github/workflows/preview-release.yml#L22

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]

⚠️ No Changeset found

Latest commit: e54b061

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

[dominikg]

set to draft because we have to update repo secrets to match this change

[github-actions]

Playground

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

[dummdidumm]

Don't think we need the probing, the chance that you run the CI and it's not on pkg.new yet is close to zero.

Who can to update the secrets and where exactly?

[dominikg]

secret howto is here https://github.com/vitejs/vite-ecosystem-ci/blob/main/docs/pr-comment-setup.md

there may be older secrets that can be deleted then, it requires admin access to sveltejs/svelte repo and sveltejs/svelte-ecosystem-ci

[dummdidumm]

The linked secrets already exist in Svelte and ecosystem-ci - not sure what needs updating?

[dominikg]

previously it was using a third party action to connect the repos through that app secret, i think we need to create a new one for the first party action it uses now

[dominikg]

@sapphi-red confirmed it can be reused, so just merging after the update in svelte-ecosystem-ci is fine.