Add the docs about kernel_launch_terminate_on_events to `RemoteMapp…

…ingKernelManager` cli options.

docs/source/operators/config-cli.md

@@ -366,4 +366,14 @@ RemoteMappingKernelManager(AsyncMappingKernelManager) options
 --RemoteMappingKernelManager.shared_context=<Bool>
     Share a single zmq.Context to talk to all my kernels
     Default: True
+--RemoteMappingKernelManager.kernel_launch_terminate_on_events=<list-item-1>...
+    Comma-separated list of dictionaries, each describing an event by `type`, `reason`, and `timeout_in_seconds`
+    (e.g. [{"type": "Warning", "reason": "FailedMount", "timeout_in_seconds": 0}]).
+    Kernel pod events will be sampled during startup, and if an event described in this list is detected,
+    the kernel launch will be terminated after the set timeout. 
+    Only available for container kernels. 
+    Make sure to provide the exact event type and reason as it appears in your container platform, 
+    A guide to finding the event type and reason in kubernetes can be found here:
+    `https://www.bluematador.com/blog/kubernetes-events-explained`
+    Default: []
 ```