add experimental remoteBindings option to getPlatformProxy docs (#23136)

* add experimental `remoteBindings` option to `getPlatformProxy` docs

* update and improve `maybeStartOrUpdateRemoteProxySession` docs

Author: dario-piotrowicz

src/content/docs/workers/development-testing/index.mdx

@@ -368,12 +368,9 @@ the bindings in an `Unstable_Config` object into a structure that can be passed
 This wrapper simplifies proxy session management. It takes:
 
 - The path to your Wrangler config, or an object with remote bindings.
-- The current proxy session details (or `null` if none).
+- The current proxy session details (this parameter can be set to `null` or not being provided if none).
 
-It returns:
-
-- `null` if no proxy session is needed.
-- An object with the proxy session details if started or updated.
+It returns an object with the proxy session details if started or updated, or `null` if no proxy session is needed.
 
 The function:
 

src/content/docs/workers/wrangler/api.mdx

@@ -300,6 +300,12 @@ const platform = await getPlatformProxy(options);
 
       **Note:** If you use `wrangler`'s `--persist-to` option, note that this option adds a subdirectory called `v3` under the hood while `getPlatformProxy`'s `persist` does not. For example, if you run `wrangler dev --persist-to ./my-directory`, to reuse the same location using `getPlatformProxy`, you will have to specify: `persist: { path: "./my-directory/v3" }`.
 
+    - `experimental` `{ remoteBindings: boolean }`
+
+      Object used to enable experimental features, no guarantees are made to the stability of this API, use at your own risk.
+
+      - `remoteBindings` Enables `getPlatformProxy` to connect to [remote bindings](/workers/development-testing/#remote-bindings).
+
 ### Return Type
 
 `getPlatformProxy()` returns a `Promise` resolving to an object containing the following fields.