[Operator] ConfigListener stale CR check only compares resource names

On ConfigListener pod restart CRs are wrongly marked as stale as the lookup only takes into account the CR name not the logical name of the cache on the server.