docs for gRPC sever timeout flag (#7400)

Test Plan: View docs page

docs/content/deployment/dagster-instance.mdx

@@ -791,3 +791,16 @@ For more information on how and why we use telemetry, please visit the <Link hre
 telemetry:
   enabled: false
 ```
+
+### Code servers
+
+The `code_servers` key lets you configure how Dagster loads the code in your [workspace](/concepts/repositories-workspaces/workspaces).
+
+When you aren't [running your own gRPC server](/concepts/repositories-workspaces/workspaces#running-your-own-grpc-server), Dagit and the Dagster Daemon load your code from a gRPC server running in a subprocess. By default, if your code takes more than 60 seconds to load, Dagster will assume that it is hanging and stop waiting for it to load. If you expect that your repository code will take longer than 60 seconds to load, you can set the `local_startup_timeout` key:
+
+```yaml file=/deploying/dagster_instance/dagster.yaml startafter=start_marker_code_servers endbefore=end_marker_code_servers
+# Configures how long Dagster waits for repositories
+# to load before timing out.
+code_servers:
+  local_startup_timeout: 120
+```

examples/docs_snippets/docs_snippets/deploying/dagster_instance/dagster.yaml

@@ -604,3 +604,12 @@ telemetry:
   enabled: false
 
 # end_marker_telemetry
+
+# start_marker_code_servers
+
+# Configures how long Dagster waits for repositories
+# to load before timing out.
+code_servers:
+  local_startup_timeout: 120
+
+# end_marker_code_servers

examples/docs_snippets/docs_snippets_tests/deploying_tests/dagster_instance_tests/snapshots/snap_test_dagster_instance.py

@@ -7,6 +7,7 @@
 snapshots = Snapshot()
 
 snapshots["test_instance_yaml 1"] = [
+    "code_servers",
     "compute_logs",
     "event_log_storage",
     "local_artifact_storage",