fix: Correct operator leader election ConfigMap lock name

[astefanutti]

Fixes the discrepancy introduced with #1741.

Release Note

NONE

[heiko-braun]

Out of curiosity, what do we need lesder election for? What leader election protocol does it use?

[astefanutti]

Out of curiosity, what do we need leader election for? What leader election protocol does it use?

It is to make sure only one operator instance operates on the controlled custom resources. Technically, it is just a ConfigMap that materialises a lock.

[astefanutti]

Adding that, on a typical production environment, an operator deployment is likely to be scaled up to achieve high availability, leading to multiple instances, among which only one can actually operates on the custom resources.