fix: form.fields.set() triggers form.fields.value() updates

[sillvva]

fixes #14680

The issue is basically that the .set() function does not trigger .value() to reactively update, because the versions state that .value() depends on is not updated. Even though the value has changed, it shows an incorrect state.

Example issue: https://stackblitz.com/edit/array-methods-308957-nxhl9tqu?file=src%2Froutes%2Ftest.remote.ts,src%2Froutes%2F%2Bpage.svelte

After fix: https://stackblitz.com/edit/array-methods-308957-ca6wdbqe?file=package.json,src%2Froutes%2F%2Bpage.svelte

---

Please don't delete this checklist! 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
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6b095b8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@sveltejs/kit	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]

Thank you - this was already fixed in #14661 (though I'm very confused why it doesn't show up as such in the diff), therefore closing.

[sillvva]

Thank you - this was already fixed in #14661 (though I'm very confused why it doesn't show up as such in the diff), therefore closing.

I thought I had the branches synced, but apparently not. 😅 I usually check prior to making a new branch.