SYSDB_OPS: Mark an entry as expired also in the timestamp cache
    
    As the cleanup task will start using new methods for searching the users
    and groups which have to be cleaned up, SSSD starts relying more in a
    more consistent state of the timestamp cache on pretty much everything
    related to the cleanup task.
    
    One of the things that would cause SSSD some problems is not having the
    ghost user expired in the persistent cache but not in the timestamp
    cache.
    
    With this patch, the entry is also expired in the timestamp cache when
    it's present.
    
    Related:
    https://pagure.io/SSSD/sssd/issue/3369
    
    Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
    
    Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
    (cherry picked from commit 9883d1e2913ff0c1db479f1ece8148e03155c7f3)