fix: correct remaining DATABRICKS_SERVING_ENDPOINT references

- Rename display string in dev-playground serving route
- Fix wrongly renamed DATABRICKS_SERVING_ENDPOINT_CLASSIFIER in docs

Signed-off-by: Pawel Kosiec <pawel.kosiec@databricks.com>

Author: pkosiec

apps/dev-playground/client/src/routes/serving.route.tsx

@@ -78,7 +78,7 @@ function ServingRoute() {
             <p className="text-muted-foreground mt-2">
               Chat with a Databricks Model Serving endpoint. Set{" "}
               <code className="text-sm bg-muted px-1 rounded">
-                DATABRICKS_SERVING_ENDPOINT
+                DATABRICKS_SERVING_ENDPOINT_NAME
               </code>{" "}
               to enable.
             </p>

docs/docs/plugins/serving.md

@@ -43,7 +43,7 @@ Endpoint aliases let you reference multiple serving endpoints by name:
 serving({
   endpoints: {
     llm: { env: "DATABRICKS_SERVING_ENDPOINT_NAME" },
-    classifier: { env: "DATABRICKS_SERVING_ENDPOINT_NAME_CLASSIFIER" },
+    classifier: { env: "DATABRICKS_SERVING_ENDPOINT_CLASSIFIER" },
   },
 })
 ```
@@ -90,7 +90,7 @@ Endpoints that don't define a streaming response schema in their OpenAPI spec wi
 |----------|-------------|
 | `DATABRICKS_SERVING_ENDPOINT_NAME` | Default endpoint name (used when `endpoints` config is omitted) |
 
-When using named endpoints, define a custom environment variable per alias (e.g. `DATABRICKS_SERVING_ENDPOINT_NAME_CLASSIFIER`).
+When using named endpoints, define a custom environment variable per alias (e.g. `DATABRICKS_SERVING_ENDPOINT_CLASSIFIER`).
 
 ## Execution context