Use extended SSSD API to signal that an entry should not be cached anymore
When ID override is changed, we remove affected entry from the schema
compat subtrees. However, we should also signal to SSSD that ID override
did change and thus SSSD should stop caching the entry. As result, next
look up of the affected entry should cause a refresh of the data in
SSSD.
This is important for cases when group membership changes for AD users.