fix: don't use console.trace inside dev warnings

[Rich-Harris]

While working on the playground console stuff I realised that we're currently doing console.trace after printing warnings in dev mode. This is because I'm a Firefox user, and Firefox doesn't include traces in warnings.

Chrome does. Since the vast majority of developers use Chrome for developing, this means unnecessary clutter. We could get fancy and detect which browser we're in but I think it's overkill.

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: 35113d1

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