[Operator] ConfigListener ignores kubernetes resource name when discovering existing Cache CRs

ConfigListener ignores the Cache CR metadata name when discovering existing Cache CRs, consequently it's possible for a new Cache CR to be generated by the ConfigListener when the original Cache CR is reconciled on the server.