Send new per-query alert count event reports for QA telemetry

[angelapwen]

This change sends a list of event reports representing the per-query alert counts from a run, appended as a field to the analyze status report, when the qa_telemetry feature flag is set. The event_report schema in the data warehouse is mimicked in the EventReport interface here.

We generate an event report just after codeql database-interpret results is run for each language, so the event reports are language-specific. The properties field of the event report is an object representing the per-query alert counts processed from a single SARIF file.

I have manually tested this by setting the environment variable CODEQL_ACTION_QA_TELEMETRY: true in a test run (GitHub internal only link) to confirm that the event report and alert counts are being generated appropriately. I have also modified the existing runQueries test to confirm that the appropriate event_report status report field is set with event property codeql database interpret-results.

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.

[angelapwen]

I've set the feature to true in the existing runQueries test, and confirmed that the appropriate event_report status report field is set with event property codeql database interpret-results.

[esbena]

and confirmed that the appropriate event_report status report field

I can see that in your test run. But it does not look like the data enters the database. Is that intentional?

database("hydro").code_scanning_v0_status_report
| where timestamp between (now(-30d) .. now())
| summarize count() by array_length(event_reports)

Results in 34035006 reports with length 0 event_reports, and nothing else.

[angelapwen]

@esbena Thank you for pointing this out. I looked at the debug logs of the run more closely and it looks like the request returned an error because I had sent the date/times for the event_report with the incorrect format. I'll put up a new PR, start a test run, and check the data warehouse for the report.