Create run from coverage

[DavertMik]

When we don't want to launch tests right now but we want to create a run in Testomat.io with corresponding tests listed
This is important when we want to launch manual tests based on report provided from coverage pipe

Ability to create new manual or end2end runs from coverage reports:

Manual run

TESTOMATIO=tstmt_... npx @testomatio/reporter run --kind manual --filter "coverage:file=coverage.manual.yml,diff=stable"

Automated run

TESTOMATIO=tstmt_... npx @testomatio/reporter run --filter "coverage:file=coverage.manual.yml,diff=stable"

See also: https://github.com/testomatio/coverage-agent

[Copilot]

Pull request overview

This PR adds the ability to create test runs in Testomat.io based on coverage reports without immediately executing tests. This enables creating manual or automated runs from coverage data, which is particularly useful for launching manual tests based on coverage analysis or scheduling automated tests for later execution.

Key changes:

• Made the command argument optional in the CLI run command, allowing run creation without test execution
• Extended coverage pipe to distinguish between suite IDs and test IDs, storing them separately and including both in run configuration
• Added coverage scope display to GitHub PR comments for manual runs, showing affected test and suite counts

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 10 comments.

File	Description
src/bin/cli.js	Made command argument optional and added logic to create runs without executing tests, including appropriate messaging based on run kind
src/pipe/testomatio.js	Added support for passing coverage configuration (tests and suites) and description to run creation parameters, plus storing runKind in the pipe store
src/pipe/github.js	Added coverage scope section to GitHub PR comments for manual runs, displaying counts of affected tests and suites
src/pipe/coverage.js	Enhanced to separately track suite IDs vs test IDs, store coverage configuration and description in pipe store, and added helper methods for building run descriptions and getting current Git branch

[olexandr13]

test:

• create runs (manual, automated)
• existing coverage docs
• github actions