Fix conflicting leaderElectionId between backup plugins

[ermakov-oleg]

Both cnpg-plugin-pgbackrest and plugin-barman-cloud currently use the same leaderElectionId, causing leader election conflicts when deployed simultaneously in the same Kubernetes cluster. This prevents organizations from using multiple backup strategies (e.g., different plugins for different PostgreSQL clusters, migration scenarios, or multi-tenant environments). Each plugin should use a unique leader election ID to enable peaceful coexistence and allow users to deploy multiple CNPG-I backup plugins without leadership conflicts.

[Agalin]

Nice finding, thanks for the PR!

Please reformat the commit, something like this should work for the first line:

fix: conflicting leaderElectionId between backup plugins

For reference, those are broken rules from the CI job:

 [commitlint] ✖   subject may not be empty [subject-empty]
[commitlint] ✖   type may not be empty [type-empty]
[commitlint] ⚠   body's lines must not be longer than 100 characters [body-max-line-length]
[commitlint] ⚠   references may not be empty [references-empty]

[Agalin]

@ermakov-oleg when fixing the message you've removed the Signed-off-by: section. Please add it back. 🙂

[ermakov-oleg]

@Agalin Fixed, thanks!