feat: implement history push mutation and enhanced MCP logging

- Implement pushHistory mutation to support pushing telemetry data to Zabbix trapper items.

- Add VERBOSITY and MCP_LOG_* environment variables for controllable request/response logging in both API and MCP server.

- Enhance ZabbixRESTDataSource with better session handling and error logging.

- Update ZabbixHistory datasource to support history push operations.

- Expand documentation with new cookbook recipes and MCP integration guides.

- Add integration tests for history pushing (src/test/history_push*).

- Reorganize documentation, moving technical product info PDF to docs/use-cases/.

- Update GraphQL generated types and VCR templates.

samples/extensions/location_tracker_devices.graphql

@@ -25,6 +25,34 @@ type DistanceTrackerDevice implements Host & Device {
     state: DistanceTrackerState
 }
 
+"""
+TrackedDevice represents a device used for simulation or tracking purposes,
+pushing its state (e.g. geojson) via Zabbix Trap.
+"""
+type TrackedDevice implements Host & Device {
+    hostid: ID!
+    host: String!
+    deviceType: String
+    hostgroups: [HostGroup!]
+    name: String
+    tags: DeviceConfig
+    inventory: Inventory
+    items: [ZabbixItem!]
+    state: TrackedState
+}
+
+type TrackedState implements DeviceState {
+    operational: OperationalDeviceData
+    current: TrackedValues
+}
+
+type TrackedValues {
+    """
+    GeoJSON representation of the tracked device's location or path.
+    """
+    geojson: JSONObject
+}
+
 """
 Represents the state of a distance tracker device.
 """