Journal mixes up remove operations and cancelling put operations

[MSDarwish2000]

Describe the bug
The expected behavior for the cache when writeFunction fails and the key has an existing value is to keep this value. The reason behind this behavior will be documented. But, the journal v1 represents this by a dirty operation followed by remove operation. This is the same behavior when deleting an existing key.
This results in missing entries when reopening the journal with possible orphan files.

To Reproduce
Steps to reproduce the behavior:

1. Put an entry into DiskLruCache
2. Re-put the same key asynchronously, throwing a cancellation exception for example
3. Close and re-open the cache

Expected behavior
The old value should be existing for this key.

System (please complete the following information):
Any system

Additional context
Not applicable