Expired event is not raised when modifying an expired entry

Due to the old way of implementing remove expired for lifespan, we didn't raise an expired event when writing to an entry. This was mostly to cause circular dependencies. But with the new remove expired max idle changes, this is now possible.

Without this change listeners can be in an inconsistent state, possibly, as the following could happen:

1. Entry is created
2. Listener is notified of creation
3. Entry expires (no event yet)
4. Entry is written to (created)
5. Listener is notified of creation.

In this case there is no intermediate state where the listener thought there was no entry. This also becomes problematic if you are listening only for events that don't include create.