fix: try catch strict_equals to avoid error accessing STATE_SYMBOL

[paoloricciuti]

Svelte 5 rewrite

Closes #13214

I'm not 100% sure with this fix but i don't think we can really do much here...it's a very niche case because you are trying to access something where you can't check if STATE_SYMBOL is there without causing trouble in the first place.

But since it's no harm i guess we can just try catch it. No test for the moment but i actually just thought of a way to test this so i'm gonna try to write a test.

Please note that the Svelte codebase is currently being rewritten for Svelte 5. Changes should target Svelte 5, which lives on the default branch (main).

If your PR concerns Svelte 4 (including updates to svelte.dev.docs), please ensure the base branch is svelte-4 and not main.

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: 7a4c06c

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

[dummdidumm]

Don't think we need a test here - comment is enough

[Xerios]

Thanks for the commit.

I wouldn't call this a niche case, these strict object restrictions are quite common for Isolated Web Apps (IWAs).
Depending on the sandboxing rules, there are plenty of other objects which would trigger same error in the same way (eg local/sessionStorage, idb, sharedworkers, cookies, clipboard api, etc...)