Changing a push model property without marking it as dirty can cause desync when the actor goes in and out of dormancy

When the actor goes out of dormancy, it will replicate its push model property, even if it hasn't been marked as dirty. In this case, it seems the value of the property is not written to the shadow state on the server.
If the property is set back to its original value (i.e. the value that was replicated before it was changed and not marked as dirty), the server won't detect that the property has changed, and so it won't be replicated to the client, causing the desync.

1. Download licensee test project from linked UDN
2. Start a PIE session with a dedicated server and client
3. Observe the logs showing the property desync between the server and client

See linked UDN for more detailed repro steps.