Cluster Max Idle can miss a touch during state transfer

The new max idle in ISPN-11020 can have an issue that when a touch command is being replicated to a write owner that isn't a read owner that the touch is missed. This can occur if a state provider node sends the entry without the touched timestamp to the new owner, but the touch command is received on the new owner before the entry is written on the new owner.

This should be a pretty small edge case, but we should close it at some point. The reason it is small is that it requires a touch command to be done at the same time as state transfer but before the state provider node but before the value is written. Then for the issue to manifest there must be a read on this new owner after the old expiration time but before the new one, without any other reads on any owners.