Debounce self-originated Hibernate cache invalidation events in Debezium Hibernate

## Context

When the application writes to the DB, it often triggers both:

1. a local cache invalidation (because the app knows it changed the entity), and
2. a CDC event consumed by the same app via Debezium, which can cause a second, redundant invalidation.

This duplication increases cache churn and can cause thundering-herd effects under write-heavy workloads.

## Proposal

We need a mechanism to debounce invalidation events that are self-originated (i.e., changes the same application instance just performed), while still honoring invalidations coming from other nodes/instances.