SYSDB: When marking an entry as expired, also set the originalModifyTimestamp to 1
    
    Resolves:
    https://pagure.io/SSSD/sssd/issue/3684
    
    If the cleanup task removes a user who was a fully resolved member (not a
    ghost), but then the group the user was a member of is requested, unless
    the group had changed, the user doesn't appear as a member of the group
    again. This is because the modify timestamp would prevent the group from
    updating and therefore the ghost attribute is not readded.
    
    To mitigate this, let's also set the originalModifyTimestamp attribute
    to 1, so that we never take the optimized path while updating the group.
    
    Reviewed-by: Fabiano Fidêncio <fidencio@redhat.com>