fix: Use `changed_at` revision when updating fields
Setting the field's revision to `current_revision` when updating is not technically wrong, but its pessimizing.
If all previous reads only observed a change of up to `changed_at`, then it's fine for us to do the same as nothing
we derive from has read from `current_revision`.