Report ML-powered query enablement in the init status report

[henrymercer]

Adds information about whether ML-powered JS queries are enabled to the init status report. This will improve our observability by allowing us to compare metrics between runs with ML-powered JS queries on and off.

Specifically, we add a ml_powered_js_queries field to the init status report that contains:

• The version string if the analysis will use a specific version of the pack
• "latest" if the analysis will use the latest version of the pack
• "false" if the analysis won't run any ML-powered JS queries, or if the analysis will run multiple ML-powered JS query packs

We report this information in the init status report rather than the analyze status report so we can gather data about timeouts.

Example status report:

{
  "workflow_run_id": 1790730464,
  "workflow_name": "Code Scanning - Action",
  "job_name": "CodeQL-Build",
  "analysis_key": ".github/workflows/codeql-analysis.yml:CodeQL-Build",
  "commit_oid": "6a99ab511b076566d0b9259a4102ac7f5c4b3e0c",
  "ref": "refs/heads/main",
  "action_name": "init",
  "action_ref": "1cddec9558c522dd219349d2149a48c46e203a8a",
  "action_oid": "unknown",
  "started_at": "2022-02-03T17:08:30.984Z",
  "action_started_at": "2022-02-03T17:08:30.984Z",
  "status": "success",
  "completed_at": "2022-02-03T17:08:37.758Z",
  "matrix_vars": "null",
  "disable_default_queries": "",
  "languages": "javascript",
  "ml_powered_js_queries": "~0.0.2" /* NEW */,
  "paths": "",
  "paths_ignore": "",
  "queries": "security-extended",
  "tools_input": "latest",
  "tools_resolved_version": "20220120",
  "workflow_languages": "javascript"
}

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.

[aeisenberg]

Just a minor thing, otherwise looks good.

[edoardopirovano]

I believe you also need a PR such as https://github.com/github/hydro-schemas/pull/1845 to add the new field to the database and also a github/github PR to propagate the fields?

[henrymercer]

I believe you also need a PR such as github/hydro-schemas#1845 to add the new field to the database and also a github/github PR to propagate the fields?

Thanks, these are in the works (see the internal tracking issue)!