Propose killing the Pepr Watch caching behavior due

[cmwylie19]

Overview

Propose killing the Pepr watch cache as it seems to create more problems that it is worth. KFC internally has a lastSeen mechanism that manages in the event of network failure or overly stale connections. Pepr seeds this with it's own tracked version of the last seen resources version per callback which is a function that uses .toString() which won't capture business logic changes in other areas of the code that function calls.

Kubernetes recommends idempotency and eventual consistency which means re-calling callback should not result in inconsistent state or failure.

Steps to reproduce

Expected result

Actual Result

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Additional Context

Add any other context or screenshots about the technical debt here.