spark clustername fix

[sanketjadhavSF]

This pull request introduces support for an explicit ClusterName field in the clusterContext struct within the Spark EKS command implementation. The main changes ensure that the cluster name is consistently sourced from this new field, improving clarity and flexibility when managing clusters.

Cluster context and configuration improvements:

• Added a new ClusterName field to the clusterContext struct to explicitly store the cluster's name.
• Updated the updateKubeConfig function to use the new ClusterName field when setting the EKS cluster name in AWS CLI arguments, replacing the previous usage of execCtx.cluster.Name.
• Modified the createSparkClients function to use the new ClusterName field when printing success messages about client creation, ensuring consistent and accurate cluster identification.

[Copilot]

Pull request overview

This PR updates the Spark-on-EKS command implementation to support an explicit cluster_name value in the Spark EKS clusterContext, and then uses that value when generating kubeconfig and when logging successful client creation.

Changes:

• Added ClusterName to the Spark EKS clusterContext (YAML/JSON: cluster_name).
• Updated aws eks update-kubeconfig invocation to use clusterContext.ClusterName.
• Updated client-creation success output to print the resolved cluster name (and removed a trailing whitespace in a comment).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.