fix: skip log_if_contains_state if only logging literals

[Rich-Harris]

To make console.log(some_state) more useful, we transform it to this, which prints a snapshot of the state along with instructions on how to do it yourself:

console.log(...$.log_if_contains_state('log', some_state));

There's no need to do this if you're just doing console.log('HERE') or console.log('WHY WONT THIS WORK') or whatever. There are doubtless other cases we could similarly optimise but literals are the obvious place to start

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: 4ccc770

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@15468