[8.x](backport #5939) [helm] derive the lease name from the release and preset names

[mergify]

What does this PR do?

This PR disables by default the kubernetes leader election unless a user explicitly marks it as enabled. More importantly this PR sets the lease name from the Helm release and the agent preset names and thus different agent deployments won't utilise the same lease now.

Why is it important?

Because it guarantees correct lease isolation across different agent deployments in the same namespace

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

N/A

How to test this PR locally

follow the kubernetes example and do two installations of the Helm chart with a different release name and under the same namespace (leases are namespace-scoped). With this PR you will see that two leases are created for the clusterWide preset where before there would be only one

Related issues

• Relates https://github.com/elastic/ingest-dev/issues/3633 as the user facing issues with the lease name is mentioned there

  ---

  This is an automatic backport of pull request [helm] derive the lease name from the release and preset names #5939 done by Mergify.

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube