ix(event-gateway): productize kafka topics capture the variables

Author: fabianrbz

app/_how-tos/event-gateway/productize-kafka-topics.md

@@ -114,14 +114,11 @@ body:
 extract_body:
   - name: id
     variable: BACKEND_CLUSTER_ID
+capture: BACKEND_CLUSTER_ID
+jq: ".id"
 {% endkonnect_api_request %}
 <!--vale on-->
 
-Export the backend cluster ID to your environment:
-```sh
-export BACKEND_CLUSTER_ID="YOUR-BACKEND-CLUSTER-ID"
-```
-
 ## Create an analytics virtual cluster
 
 Use the following command to create the first virtual cluster for the `analytics` category:
@@ -155,17 +152,13 @@ body:
 extract_body:
   - name: id
     variable: ANALYTICS_VC_ID
+capture: ANALYTICS_VC_ID
+jq: ".id"
 {% endkonnect_api_request %}
 <!--vale on-->
 
 This virtual cluster provides access to topics with the `analytics_` prefix, and the `user_actions` topic.
 
-Export the virtual cluster ID to your environment:
-
-```sh
-export ANALYTICS_VC_ID="YOUR-ANALYTICS-VIRTUAL-CLUSTER-ID"
-```
-
 ## Create a payments virtual cluster
 
 Now create the `payments` virtual cluster:
@@ -199,16 +192,13 @@ body:
 extract_body:
   - name: id
     variable: PAYMENTS_VC_ID
+capture: PAYMENTS_VC_ID
+jq: ".id"
 {% endkonnect_api_request %}
 <!--vale on-->
 
 This virtual cluster will be used to access topics with the `payments_` prefix, and the `user_actions` topic.
 
-Export the virtual cluster ID to your environment:
-```sh
-export PAYMENTS_VC_ID="YOUR-PAYMENTS-VIRTUAL-CLUSTER-ID"
-```
-
 ## Create an analytics listener with a policy
 
 For testing purposes, we'll use **port forwarding** to route traffic to each virtual cluster.  
@@ -230,14 +220,11 @@ body:
 extract_body:
   - name: id
     variable: ANALYTICS_LISTENER_ID
+capture: ANALYTICS_LISTENER_ID
+jq: ".id"
 {% endkonnect_api_request %}
 <!--vale on-->
 
-Export the listener ID to your environment:
-```sh
-export ANALYTICS_LISTENER_ID="YOUR-ANALYTICS-LISTENER-ID"
-```
-
 Create the [port mapping policy](/event-gateway/policies/forward-to-virtual-cluster/):
 
 <!--vale off-->
@@ -274,13 +261,11 @@ body:
 extract_body:
   - name: id
     variable: PAYMENTS_LISTENER_ID
+capture: PAYMENTS_LISTENER_ID
+jq: ".id"
 {% endkonnect_api_request %}
 <!--vale on-->
 
-Export the listener ID to your environment:
-```sh
-export PAYMENTS_LISTENER_ID="YOUR-PAYMENTS-LISTENER-ID"
-```
 Create the port mapping policy:
 
 <!--vale off-->