docs: update $effect examples

[benmccann]

Updates examples to remove things that could possibly be confusing or misleading

Mostly replaces console.log with writes to canvas. Users should typically reach for $inspect instead of console.log

Also replaces the example that was setting count inside setInterval inside an $effect. I tried telling a generally advanced user yesterday that you shouldn't set state inside an $effect and he responded "what are you talking about? that's what one of the very first examples shows..."

[changeset-bot]

⚠️ No Changeset found

Latest commit: 120a062

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-svelte-15463-svelte.vercel.app/

[github-actions]

Playground

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

[Rich-Harris]

Also replaces the example that was setting count inside setInterval inside an $effect. I tried telling a generally advanced user yesterday that you shouldn't set state inside an $effect

Setting count inside a setInterval isn't 'setting state inside an effect', it's setting state inside an interval which is a different (and totally fine) thing. We should revert that change

[Rich-Harris]

preview deployment is failing but i suspect it's unrelated