[BUG] matchField does not re-evaluate when the other field is changed

[Max]

Describe the bug
When using matchField, if you enter a value into the field with the validator it will be marked as invalid, and then when you match the value in the field without the validator it stays invalid.

To Reproduce
Steps to reproduce the behavior:

1. Create basic match field as per docs
2. Type 'password' into the passwordConfirmation field
3. Type 'password' into the password field
4. The passwordConfirmation field is still invalid

Expected behavior
When the first field obtains a value which is the same as the field with the validator, the field should be marked as valid.