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

I guess nobody will do something like

letarr=$state([1,2,3]);arr.shift=()=>{thrownewError()};// will make $inspect deferred until a successful call of array mutating method$inspect(arr);// laterarr.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 testinspect-console-trace - the error stack was expected to haveat 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 withfeat:,fix:,chore:, ordocs:.
• 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 withinpackages/svelte/src, add a changeset (npx changeset).

Tests and linting

• Run the tests withpnpm test and lint the project withpnpm lint