Add schema table with explicit data types for query_log fields

[Copilot]

Replaced categorized bullet list with structured schema table for the query_log table's 21 fields.

Changes

• Schema documentation: Bulleted prose → 3-column table (Column | Data type | Description)
• Type coverage: Added explicit data types for all fields (timestamp, string, int64)
• Completeness: Enumerated all fields individually vs. grouped categories with vague "and ingester-related fields"

Before

- **Timing**: `time` (timestamp), `query_issue_time_ns`, `permit_duration_ns`, ...
- **Resource usage**: `partition_count`, `parquet_file_count`, `max_memory_bytes`, and ingester-related fields.

After

| Column | Data type | Description |
| :----- | :-------- | :---------- |
| **time** | timestamp | Timestamp when the query log entry was recorded |
| **query_issue_time_ns** | int64 | Time when the query was issued (nanoseconds) |
| **permit_duration_ns** | int64 | Time spent waiting for query permit (nanoseconds) |
| **partition_count** | int64 | Number of partitions accessed |
| **parquet_file_count** | int64 | Number of Parquet files read |
| **max_memory_bytes** | int64 | Maximum memory used during query execution (bytes) |

Impact

• Developer UX: Quick reference for SQL query construction
• LLM consumption: Structured data for markdown generation pipeline (TurndownService preserves tables)
• Tooling: Machine-readable schema for SDK/type generation

Preserves existing note about success/running being string-typed ('true'/'false'), not boolean.

Original prompt

Pull request: https://github.com/influxdata/docs-v2/pull/6866/files

At line 131, the section describes fields. Should we include a schema or data type table for clarity?

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[ritwika314]

lgtm, Thank you!