fix(secrets): show a renamed variable as a variable before save

The rename carried visibility into the save payload but not into the
render, which still resolved disclosure from server state only. The new
name has no server visibility yet, so the row defaulted to secret: it
jumped into Workspace secrets and bullet-masked a value the member can
plainly read, until save landed.

Author: mzxchandra

apps/sim/app/workspace/[workspaceId]/settings/components/secrets/components/secrets-manager/secrets-manager.tsx

@@ -904,9 +904,19 @@ export function SecretsManager() {
     return entries.map(([key, value]) => ({
       key,
       value,
-      visibility: visibilityMap[key] ?? ('secret' as EnvVisibility),
+      // A pending rename is checked FIRST: the new name has no server-side
+      // visibility yet, so falling straight through to `visibilityMap` would
+      // default it to `secret` — bouncing the row into Workspace secrets and
+      // bullet-masking a value the member can plainly read, until save lands.
+      visibility: renamedKeyVisibility[key] ?? visibilityMap[key] ?? ('secret' as EnvVisibility),
     }))
-  }, [searchTerm, filteredWorkspaceEntries, workspaceVars, workspaceEnvData?.visibility])
+  }, [
+    searchTerm,
+    filteredWorkspaceEntries,
+    workspaceVars,
+    workspaceEnvData?.visibility,
+    renamedKeyVisibility,
+  ])
 
   /**
    * Renders one workspace section. Both sections share the row component and