read-cache-after-write consistency and event filtering for deletes

See also parent issue.

This might be a bit problematic, for resource without finalizer:

If the resource does not implement a finalizer, we could just record the UID of the resource and filter out events until we receive the delete event, that removes the cached resource ID.

The issue is with the resources with a finalizer, there we could define this like:

1. Filter just the event that was caused by the delete operation (in this case, it just adds the deletion timestamp), and process subsequent events. By definition, only operations should happen afterwards, and that includes finalizer removals, but that is not enforced on the API level. Note that implementation-wise, this is an issue since the delete operation does not return the new resource nor it's version.

2. We could filter out all the subsequent events until we receive a delete event. - But this might be too opionated, and especially if the controller would be restarted, users might see the resources again (although still marked for deletion). So probably not the right thing to do.

Notes:

• optimistic locking does not seems to work for deletes either

Commencez par localiser les chemins du cache de lecture et du filtrage des événements pour les opérations de suppression dans Java Operator SDK, puis consultez l’issue parente pour connaître le comportement attendu. Comparez les ressources avec et sans finalizers ainsi que la remarque sur le verrouillage optimiste ; cette issue ne sera terminée qu’une fois la stratégie de filtrage des événements de suppression décidée et implémentée de manière cohérente.