fix(playwright): recognize modern screenshot comparison errors

[dimazollo]

Playwright 1.59.1 reports screenshot mismatches as:

Error: expect(page).toHaveScreenshot(expected) failed

The adapter only recognizes Screenshot comparison failed, so it marks these as general errors even when expected/actual/diff images are attached. Accept can then leave a stale error instead of resolving the visual failure.

This adds support for the newer page/locator toHaveScreenshot header. Playwright uses the same header when it cannot take a screenshot, so the adapter also checks for matching expected/actual/diff attachments. The old Screenshot comparison failed handling stays unchanged.

Only the adapter and its unit tests change. toMatchSnapshot, changes to legacy mixed-error handling, and platform handling are outside this PR.

Reproduction

With Playwright 1.59.1 and html-reporter/playwright:

import {test, expect} from '@playwright/test';

test('screenshot mismatch', async ({page}) => {
    const color = process.env.CHANGED ? 'blue' : 'red';
    await page.setContent(`<div style="width:120px;height:80px;background:${color}"></div>`);
    await expect(page).toHaveScreenshot('example.png');
});

npx playwright test --update-snapshots
CHANGED=1 npx playwright test

Before: error / Error. After: fail / ImageDiffError.

Tests

• All 30 adapter tests pass, including page/locator diffs, capture failures, snapshot attachment matching, unnamed diffs, ANSI formatting, and multiple soft screenshot assertions.
• npm test passes on Node 20.19.6: lint, Node and jsdom unit tests, and type checks.

The full GUI e2e suite and interactive Accept/Undo weren't rerun for this isolated fix.

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en.

[sipayRT]

why is it not enough to just switch to 2 error options? for example, /Screenshot comparison failed|expect\(.*\)\.toHaveScreenshot\(expected\)failed/

[dimazollo]

Playwright uses the same header when it cannot take a screenshot. So I also check that expected, actual, and diff images are attached.

I'll keep toHaveScreenshot support with this check and remove the mixed-error changes from this PR.

[sipayRT]

toMatchSnapshot should be used for non-image comparison, so we don't need this part here

[dimazollo]

It can compare images too, but I agree that we don't need it for this fix. I'll remove it from this PR.