LGP: Fix bug with enableLGPDeploymentHealthCheck=true and add operator.enabled (#157)

Author: andrewnguonly

src/langgraph-platform/deploy-hybrid.mdx

@@ -52,20 +52,22 @@ Before deploying, review the [conceptual guide for the Hybrid](/langgraph-platfo
         smithBackendUrl: "https://api.smith.langchain.com" # Only override this if on EU
         langgraphListenerId: "" # Listener ID from Step 2-6
         watchNamespaces: "" # comma-separated list of Kubernetes namespaces that the listener and operator will deploy to
-        enableLGPDeploymentHealthCheck: "true" # enable/disable health check step for deployments
+        enableLGPDeploymentHealthCheck: true # enable/disable health check step for deployments
 
       ingress:
         hostname: "" # specify a hostname that will be configured for all deployments
 
       operator:
-        createCRDs: true # set this to `false`, if the CRD has been previously installed
+        enabled: true # set this to `false` if the operator is already deployed in the current Kubernetes namespace
+        createCRDs: true # set this to `false` if the CRD has been previously installed in the current Kubernetes cluster
     ```
     - `config.langsmithApiKey`: The `langgraph-listener` deployment authenticates with LangChain's LangGraph control plane API with the `langsmithApiKey`.
     - `config.langsmithWorkspaceId`: The `langgraph-listener` deployment is coupled to LangGraph Server deployments in the LangSmith workspace. In other words, the `langgraph-listener` deployment can only manage LangGraph Server deployments in the specified LangSmith workspace ID.
     - `config.langgraphListenerId`: In addition to being coupled with a LangSmith workspace, the `langgraph-listener` deployment is also coupled to a listener. When a new LangGraph Server deployment is created, it is automatically coupled to a `langgraphListenerId`. Specifying `langgraphListenerId` ensures that the `langgraph-listener` deployment can only manage LangGraph Server deployments that are coupled to `langgraphListenerId`.
     - `config.watchNamespaces`: A comma-separated list of Kubernetes namespaces that the `langgraph-listener` deployment will deploy to. This list should match the list of namespaces specified in step 2-4.
     - `config.enableLGPDeploymentHealthCheck`: To disable the LangGraph Server health check, set this to `false`.
     - `ingress.hostname`: As part of the deployment workflow, the `langgraph-listener` deployment attempts to call the LangGraph Server health check endpoint (`GET /ok`) to verify that the application has started up correctly. A typical setup involves creating a shared DNS record or domain for LangGraph Server deployments. This is not managed by LangGraph Platform. Once created, set `ingress.hostname` to the domain, which will be used to complete the health check.
+    - `operator.enabled`: There can only be 1 instance of the `langgraph-platform-operator` deployed in a Kubernetes namespace. Set this to `false` if there is already an instance of `langgraph-platform-operator` deployed in the current Kubernetes namespace.
     - `operator.createCRDs`: Set this value to `false` if the Kubernetes cluster already has the `LangGraphPlatform CRD` installed. During installation, an error will occur if the CRD is already installed. This situation may occur if multiple listeners are deployed on the same Kubernetes cluster.
 5. Deploy `langgraph-dataplane` Helm chart.
     ```bash