Add support for asymmetric matcher types

[porada]

What

The following matchers currently force casts on their arguments, even though they shouldn’t:

expect(link).toHaveAttribute({
    rel: expect.stringContaining('opener') as unknown
});

expect(form).toHaveFormValues({
    foo: 'bar',
    baz: expect.any(Number) as unknown
});

expect(element).toHaveStyle({
    display: expect.any(String) as unknown
    width: 1024,
});

Why

Casts add noise to otherwise valid expectations. Asymmetric matchers are a native feature in all supported test frameworks, so they shouldn’t require workarounds.

How

This PR widens the argument types from unknown to any, allowing asymmetric matcher values to be passed directly:

expect(link).toHaveAttribute({
    rel: expect.stringContaining('opener') // ✅
});

expect(form).toHaveFormValues({
    baz: expect.any(Number) // ✅
});

expect(element).toHaveStyle({
    display: expect.any(String) // ✅
});

Checklist

• Documentation
• Tests
• Updated type definitions
• Ready to be merged

[porada]

I didn’t tick Documentation as this PR doesn’t affect docs.