[App Rotuer] Inconsistent Client Scope with shallow app routing

### Problem:
There is no painless and non-deprecated way to invalidate client scope data when using shallow routing.

When navigating to a new page in shallow routing mode, the values in the client scope are not updated if they have changed to default values, because serialize returns only the modified values and hack inject updates the values based on them.

### Process Illustration:

https://github.com/user-attachments/assets/4944b691-86a8-45e4-81ff-93a8e1b500b5

### Expected Result:
During navigation, if the value of any store has been changed to the default value, it should be invalidated in the client scope.

### Reproduction:
https://github.com/Krakazybik/effector-shallow-routing-inconsistency/tree/main