Use agent name as the helm release name in the generated command

What does this MR do and why?

The MR sets the agent name in the agent installation instructions to minimize the risk of conflicts in case the user installs multiple agents in the same cluster.

Screenshots or screen recordings

Before	After

How to set up and validate locally

1. Visit Infrastructure -> Kuberenetes clusters page.
2. On the top actions button select Connect a cluster.
3. Proceed through the modal by typing a unique name for the new agent.
4. After the token is created you'll see the command for the agent installation into the cluster. Validate that the command includes the agent name.
5. Go to the newly created agent page and select the Access tokens tab.
6. Select Create new token and validate that the command includes your agent's name.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Closes #363141 (closed)