Make `dirty` revert to false if original value is restored

Describe the problem

The current behavior of dirty on a remote form is, as documented, "Whether the field or any nested field has been edited since the form was mounted". When you're using it to prevent navigation with a confirm dialog, if you modify a field and then turn it back to its original value, it's still considered dirty (and hence the whole form).

This causes the confirm dialog to pop up even if there are no obvious changes.

Describe the proposed solution

Make dirty take the original state of the form into account, so if a value changes back to its original, it's not considered dirty anymore.

Alternatives considered

No response

Importance

would make my life easier

Additional Information

No response

Locate the remote form implementation that computes the dirty state and its related tests; the issue does not name specific files or test cases. First trace how the original form state is stored and how field changes are compared. Done means restoring a field's original value no longer leaves the field or form dirty, while genuinely changed values still do.