docs: fix the example docs related to set execution api (actions) (#10359)

# Which Problems Are Solved

Fix docs related to Actions V2 SetExecution API
[endpoint](https://zitadel.com/docs/apis/resources/action_service_v2/action-service-set-execution)

# How the Problems Are Solved

The examples are updated

# Additional Changes
N/A

# Additional Context
- Closes #10320

docs/docs/guides/integrate/actions/testing-event.md

@@ -103,9 +103,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-function-manipulation.md

@@ -129,9 +129,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-function.md

@@ -107,9 +107,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-request-manipulation.md

@@ -154,9 +154,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-request-signature.md

@@ -114,9 +114,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-request.md

@@ -107,9 +107,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-response-manipulation.md

@@ -173,9 +173,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/testing-response.md

@@ -107,9 +107,7 @@ curl -L -X PUT 'https://$CUSTOM-DOMAIN/v2beta/actions/executions' \
         }
     },
     "targets": [
-        {
-            "target": "<TargetID returned>"
-        }
+        "<TargetID returned>"
     ]
 }'
 ```

docs/docs/guides/integrate/actions/usage.md

@@ -406,17 +406,11 @@ If you then have a call on `/zitadel.user.v2.UserService/UpdateHumanUser` the fo
 
 And if you use a different service, for example `zitadel.session.v2.SessionService`, then the `all` Execution would still be used.
 
-### Targets and Includes
+### Targets
 
-:::info
-Includes are limited to 3 levels, which mean that include1->include2->include3 is the maximum for now.
-If you have feedback to the include logic, or a reason why 3 levels are not enough, please open [an issue on github](https://github.com/zitadel/zitadel/issues) or [start a discussion on github](https://github.com/zitadel/zitadel/discussions)/[start a topic on discord](https://zitadel.com/chat)
-:::
+An execution can contain only a list of Targets, and Targets are comma separated string values.
 
-An execution can not only contain a list of Targets, but also Includes.
-The Includes can be defined in the Execution directly, which means you include all defined Targets by a before set Execution.
-
-If you define 2 Executions as follows:
+Here's an example of a Target defined on a service (e.g. `zitadel.user.v2.UserService`)
 
 ```json
 {
@@ -426,13 +420,12 @@ If you define 2 Executions as follows:
     }
   },
   "targets": [
-    {
-      "target": "<TargetID1>"
-    }
+    "<TargetID1>"
   ]
 }
 ```
 
+Here's an example of a Target defined on a method (e.g. `/zitadel.user.v2.UserService/AddHumanUser`)
 ```json
 {
   "condition": {
@@ -441,21 +434,13 @@ If you define 2 Executions as follows:
     }
   },
   "targets": [
-    {
-      "target": "<TargetID2>"
-    },
-    {
-      "include": {
-        "request": {
-          "service": "zitadel.user.v2.UserService"
-        }
-      }
-    }
+    "<TargetID2>",
+    "<TargetID1>"
   ]
 }
 ```
 
-The called Targets on "/zitadel.user.v2.UserService/AddHumanUser" would be, in order:
+The called Targets on `/zitadel.user.v2.UserService/AddHumanUser` would be, in order:
 
 1. `<TargetID2>`
 2. `<TargetID1>`