fix: gracefully handle non-positive Qase IDs in runtime APIs

[gibiw]

Summary

Follow-up to #973. The previous PR filtered non-positive Qase test case IDs at the parser layer (parseQaseIdsFromString, parseProjectMappingFromTitle, parseProjectMappingFromTags, and three reporter-local parsers). A user reported that qase.id(0) in playwright still produced HTTP 400 — and they were right.

Root cause: playwright and wdio expose runtime metadata APIs that write IDs into test metadata directly, bypassing all parsers:

Reporter	API	Side-effect
playwright	`qase(0, name)`	`PlaywrightQaseReporter.addIds([0], "...")` → registry override
playwright	`qase.id(0)`	`addMetadata({ ids: [0] })` — primary culprit reported by user
playwright	`qase.projects({ PROJ1: [0] })`	`addMetadata({ projectMapping: { PROJ1: [0] } })`
wdio	`qase.id(0)`	`process.emit('addQaseID', { ids: [0] })`

Other reporters (jest, mocha, cypress, wdio's `qase()`) only build titles like `"name (Qase ID: 0)"` which were already filtered by the parser fix — they don't need changes.

Fix

Apply `filterPositiveIds()` (already exported from `qase-javascript-commons/internal`) in each runtime API. If everything filters out, the metadata attach / event emit is skipped entirely (no point writing empty metadata that would shadow the absence of an ID).

Verified end-to-end

Created an example playwright spec covering all four formats from the user's bug report and ran it with the locally-built reporter (`QASE_MODE=off`). Output:
```
✓ Format 1: qase(0, name)
✓ Format 2: qase.id(0) inside test
✓ Format 3: annotation QaseID = "0"
✓ Format 4: qase.projects with zero IDs
4 passed (1.2s)
```
Each emits the expected `[qase] Warning: Qase test case ID must be greater than 0, got "0"` and the test result is reported without an ID (the user's bug — HTTP 400 — no longer reproduces).

Test plan

• `npm test` in `qase-playwright` — 98/98 (6 new regression tests for `qase()`, `qase.id()`, `qase.projects()` with non-positive IDs)
• `npm test` in `qase-wdio` — 99/99 (4 new tests for `qase.id()`)
• `npm run build` — both packages build with the new commons `~2.7.4` pin
• Manual end-to-end repro of the user's bug — no HTTP 400, warning emitted, result reported without ID

Versions

• `playwright-qase-reporter` 2.5.3 → 2.5.4
• `wdio-qase-reporter` 1.5.3 → 1.5.4
• Commons pin updated to `~2.7.4` in both.