[ci-stats] add Client class for accessing test group stats

[spalger]

In order to support pulling test group stats from ci-stats in Kibana code I'd like to add a new CiStatsClient class which exposes non-reporter methods (mostly so we don't bloat or complicate the reporter). This currently just includes one method:

CiStatsClient#getLatestTestGroupStats({
  /** The Kibana branch to get stats for, eg "main" */
  branch: string;
  /** The CI job names to filter builds by, eg "kibana-hourly" */
  ciJobNames: string[];
  /** Filter test groups by group type */
  testGroupType?: string;
})

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[spalger]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 4c11c6e
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/dev-utils	193	200	+7

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
@kbn/dev-utils	0	1	+1

Unknown metric groups

API count

id	before	after	diff
@kbn/dev-utils	275	281	+6

History

• 💚 Build #22990 succeeded 5322ece

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.0
✅	8.1
✅	7.17

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation