Output dropped Creation/Update/Delete events when failed to sync Kong configuration by go-database-reconciler

## Problem Statement

In cases when error happens on syncing Kong configuration by GDR (For example, uploading configuration to KIC in Konnect CP), some events are dropped and not applied after error happen. To reduce the confusion, we should output the dropped events after bumping GDR version to include https://github.com/Kong/go-database-reconciler/pull/362.

## Proposed Solution

Collect dropped events from GDR and output them in either way (or both):
- Add k8s events to related objects
- Output them in logs

## Additional Information

...

## Acceptance Criteria

- [ ] Users can knowt the events are dropped in syncing by either:
- [ ] Events attached to related k8s resource
- [ ] Logs of KO

The issue names no files or tests; start by locating the go-database-reconciler integration and the code that handles Kubernetes events and logs during configuration sync. Reproduce a sync failure, then verify that dropped Creation, Update, and Delete events are visible through at least one accepted output path.

Written by the indexing model from the issue text.