Quent Task Instrumentation (#809)

Defines a task model based on the Sirius' execution semantics, and adds
instrumentation to capture information about task events.

Also add basic analyzers that [quent](github.com/rapidsai/quent) can use
to generate query timelines for tasks.

Notes

- This PR instruments the task lifecycle, not the new scan split
lifecycle.
- The new upstream scan path is covered because
`sirius_gpu_scan_operator::execute()` still runs under
`gpu_pipeline_task`.
- Split production, footer reads, and row-group pruning happen before
task creation and
    remain outside the task FSM.

Author: dhruv9vats

CMakeLists.txt

@@ -263,6 +263,7 @@ set(EXTENSION_SOURCES
     src/parallel/task_executor.cpp
     src/pipeline/gpu_pipeline_executor.cpp
     src/pipeline/gpu_pipeline_task.cpp
+    src/pipeline/sirius_pipeline_itask.cpp
     src/pipeline/task_scheduler.cpp
     src/pipeline/sirius_meta_pipeline.cpp
     src/pipeline/sirius_pipeline.cpp

docs/super-sirius/configuration.md

@@ -212,7 +212,74 @@ sirius:
 | `output_directory` | string | `telemetry_data` | Directory for Quent ndjson files. |
 | `engine_name` | string | `siriusDB` | Engine name reported in engine-level telemetry. |
 
-Per-query labels are configured separately with `CALL sirius_set_query_label(...)` SQL function or the `query_label` named parameter on `gpu_execution(...)`.
+Per-query labels are configured separately from YAML. They can be set with the
+`sirius_set_query_label` SQL function or inline with the `query_label` named
+parameter on `gpu_execution(...)`:
+
+```sql
+-- Applies to the next Sirius query, including transparent plain-SQL execution.
+CALL sirius_set_query_label('tpch_q1_iter1');
+SELECT *
+FROM lineitem
+WHERE l_orderkey < 100;
+
+-- Inline label for an explicit gpu_execution call.
+CALL gpu_execution(
+  'SELECT * FROM lineitem WHERE l_orderkey < 100',
+  query_label = 'tpch_q1_iter1'
+);
+```
+
+`sirius_set_query_label` is consumed once by the next Sirius query. For explicit
+`gpu_execution(...)`, an inline `query_label` parameter takes precedence over a
+pending label set with `sirius_set_query_label`.
+
+### Generating Query Telemetry
+
+To generate telemetry from Sirius queries, update the Sirius config file used by
+the query run and enable Quent export:
+
+```yaml
+sirius:
+  telemetry:
+    enable_quent: true
+    output_directory: telemetry_data
+    engine_name: siriusDB
+```
+
+Load that config through the normal config resolution path, usually by setting
+`SIRIUS_CONFIG_FILE=/path/to/sirius.yaml`. Any Sirius query run with
+`enable_quent: true` writes Quent ndjson files into `output_directory`.
+
+For TPC-H Parquet runs, the helper script runs queries and labels each
+`(query, iteration)` pair before executing it:
+
+```bash
+pixi run -- ./test/tpch_performance/run_tpch_parquet_and_generate_telemetry.sh \
+  --iterations 1 \
+  --parquet-dir /data/tpch/sf100/p16/zstd-8/ \
+  100
+```
+
+Pass `--config <path>` to use a full Sirius config. If no query numbers are
+provided, the script runs all 22 TPC-H queries.
+
+Start the Quent analyzer server over the same telemetry directory to view the
+captured telemetry:
+
+```bash
+pixi run quent
+```
+
+The `quent` Pixi task defaults to `telemetry_data`, and runs the telemetry
+server with the UI enabled. If the config uses a different `output_directory`,
+pass that path as the task argument:
+
+```bash
+pixi run quent /path/to/telemetry_data
+```
+
+Then open `http://localhost:8080` and select the captured Sirius engine/query.
 
 ## Thread Pool Configuration
 

pixi.toml

@@ -52,6 +52,11 @@ go-cgo = ">=1.25"
 
 [tasks]
 
+[tasks.quent]
+description = "Run the Quent telemetry UI server."
+cmd = "echo 'Quent UI will be served at: http://localhost:8080' && cargo run --manifest-path rust/Cargo.toml -p sirius-telemetry-server --features ui -- --output-dir {{ output_dir }}"
+args = [{ arg = "output_dir", default = "telemetry_data" }]
+
 # CUDA version features: use `pixi run -e cuda12` for CUDA 12.x systems
 [feature.cuda13.system-requirements]
 cuda = "13"