fix(cli): use raw cluster name for remote kubeconfig path lookup (!25)

Closes NVIDIA#28

## Summary
- `--update-kube-config` and `--get-kubeconfig` appended a `-remote` suffix to the cluster name when resolving the stored kubeconfig path, but the deploy step writes the kubeconfig under the raw name — so the suffixed path never existed, causing both flags to fail for remote clusters.
- Removed the suffix logic so the lookup path matches the deploy path. The `-remote` suffix is still applied to internal kubeconfig YAML entries (cluster/context/user names) by `rewrite_kubeconfig_remote`, which is unaffected.
- Inlined the `is_remote` variable since it was only used to compute the display-only `location` string.

Author: drew

crates/navigator-cli/src/run.rs

@@ -672,8 +672,7 @@ pub async fn cluster_admin_deploy(
     remote: Option<&str>,
     ssh_key: Option<&str>,
 ) -> Result<()> {
-    let is_remote = remote.is_some();
-    let location = if is_remote { "remote" } else { "local" };
+    let location = if remote.is_some() { "remote" } else { "local" };
 
     let mut options = DeployOptions::new(name);
     if let Some(dest) = remote {
@@ -714,13 +713,7 @@ pub async fn cluster_admin_deploy(
 
     if update_kube_config {
         let target_path = default_local_kubeconfig_path()?;
-        // For remote clusters, the name includes "-remote" suffix
-        let kubeconfig_name = if is_remote {
-            format!("{name}-remote")
-        } else {
-            name.to_string()
-        };
-        update_local_kubeconfig(&kubeconfig_name, &target_path)?;
+        update_local_kubeconfig(name, &target_path)?;
         eprintln!(
             "{} Updated kubeconfig at {}",
             "✓".green().bold(),
@@ -729,12 +722,7 @@ pub async fn cluster_admin_deploy(
     }
 
     if get_kubeconfig {
-        let kubeconfig_name = if is_remote {
-            format!("{name}-remote")
-        } else {
-            name.to_string()
-        };
-        print_kubeconfig(&kubeconfig_name)?;
+        print_kubeconfig(name)?;
     }
 
     print_deploy_summary(name, &handle);