fix(fleetops): repair three broken variable chains

postman/collections/Fleetbase API/Contacts/Update a Contact.request.yaml

@@ -17,7 +17,6 @@ body:
         "title": "Mr",
         "email": "john@exampleco.com",
         "phone": "563-920-4264",
-        "type": "technician",
         "meta": {
             "external_ref": "john-doe"
         }

postman/collections/Fleetbase API/Labels/Render Label.request.yaml

@@ -5,7 +5,8 @@ method: GET
 
 pathVariables:
   - key: id
-    value: "{{label_subject_id}}"
+    value: "{{order_id}}"
+    description: The order, waypoint or entity to render a label for, matching `type` below.
 
 queryParams:
   format: "stream"

postman/collections/Fleetbase API/Order Configs/Query Order Configs.request.yaml

@@ -5,5 +5,17 @@ url: "{{base_url}}/{{namespace}}/order-configs"
 method: GET
 headers:
   Accept: application/json
+scripts:
+  - type: afterResponse
+    code: |-
+      // Retrieve an Order Config addresses {{order_config_id}}. It used to set that
+      // itself in its own afterResponse, which cannot work — the value has to exist
+      // before the request is sent. This listing runs first, so it is the natural source.
+      var json_response = pm.response.json();
+
+      if (Array.isArray(json_response) && json_response.length) {
+          pm.environment.set("order_config_id", json_response[0].id);
+      }
+    language: text/javascript
 
 order: 1000