fix: better handle $inspect on array mutations

[7nik]

Fixes #16375, and now $inspect is called only once per array-mutating method.

I guess nobody will do something like

let arr = $state([1, 2, 3]);
arr.shift = () => { throw new Error() }; // will make $inspect deferred until a successful call of array mutating method
$inspect(arr);
// later
arr.shift();

or in another way make the methods throwable because it's shooting into one's own leg.

Also, Array.prototype.shift.call(arr) will still trigger $inspect on each step. But patching the Array prototype is too much?

About the test inspect-console-trace - the error stack was expected to have at HTMLButtonElement.<anonymous> (path) but now it isn't in the last 10 stack calls.

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: 5273f70

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

[Rich-Harris]

love this fix