Remove mermaid nav from workload isolation diagrams

Author: katmayb

src/langsmith/workload-isolation.mdx

@@ -25,7 +25,7 @@ This is the default model and recommended choice for most customers.
 
 This model (single workspace per team) uses a single organization as the top-level boundary. Within the organization, multiple workspaces are used to isolate different teams or business units. Each workspace represents a logical boundary for a specific team and governs which data and resources that team can access. Within a workspace, teams use multiple applications to group together resources that support the same agent. An application may also contain distinct resources, such as separate tracing projects, for development and production environments.
 
-```mermaid
+```mermaid actions={false}
 graph LR
     Org[Organization]
 
@@ -75,7 +75,7 @@ graph LR
 
 In this model (multiple teams per workspace), multiple teams share a single workspace within an organization and use applications and [ABAC](/langsmith/organization-workspace-operations#access-policies) to separate resources and govern access. As a result, shared resources such as [prompts](/langsmith/prompt-engineering) and [deployments](/langsmith/deployment) can be reused across teams, while access to sensitive resources like [traces](/langsmith/observability-concepts#traces) and [datasets](/langsmith/evaluation-concepts#datasets) is limited to the owning team.
 
-```mermaid
+```mermaid actions={false}
 graph LR
     Org[Organization]
 
@@ -129,7 +129,7 @@ This approach should be used only when strict isolation is required.
 
 In this model (multiple workspaces per team), isolation is increased by creating multiple workspaces for a single team. Workspaces may be organized by project or by environment, such as separate development and production workspaces. Each workspace is fully isolated, with its own users, data, and resources, and access is strictly scoped to that workspace.
 
-```mermaid
+```mermaid actions={false}
 graph LR
     Org[Organization]