Add actions-specific telemetry fields

[aeisenberg]

Ensures we are sending proper events to our telemetry processor when we run actions queries.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.

[Copilot]

Pull Request Overview

This PR adds new telemetry fields to the QueriesStatusReport interface so that actions-specific query execution and result interpretation durations can be captured and sent to the telemetry processor.

• Adds the field analyze_builtin_queries_actions_duration_ms with updated JSDoc comments.
• Adds the field interpret_results_actions_duration_ms with corresponding documentation updates.

Comments suppressed due to low confidence (2)

src/analyze.ts:51

• Consider adding unit tests that verify the telemetry event includes the new actions-specific query duration field.

analyze_builtin_queries_actions_duration_ms?: number;

src/analyze.ts:109

• Consider adding tests to validate that the result interpretation duration for actions is correctly captured and propagated to telemetry.

interpret_results_actions_duration_ms?: number;

[aeisenberg]

Thanks for the reviews. The failures look transient.