Alternative approach to guarantee primary updates for next reconiliation

[csviri]

In v5.1 we provided a feature that guarantees primary update for next reconiliation:
https://javaoperatorsdk.io/blog/2025/05/22/how-to-guarantee-allocated-values-for-next-reconciliation/
using an additional cache.

An alternative approach would be without cache, to do the update the same way (this with optimistic locking) , just without caching the resource explicitly. Instead, polling the cache until the a new resource version is recieved.

The pros of this approach is simplicity, and we might argue that also a little bit memory efficient, but since in practice the additional cached resource is quickly evicted. On other other side if the informer watch looses connection, it might take some time to fully sync again, so the polling of the cache could extend the reconiliation time.