[Bug]: getByRole() with a regex name and a string description prints the raw internal:role selector

Nobody has claimed this yet.

### Version

1.61.0 and later, still on main

### Steps to reproduce

```js
test('repro', async ({ page }) => {
console.log(`${page.getByRole('button', { name: /Delete/i, description: 'Removes the item' })}`);
console.log(`${page.getByRole('row', { name: 'Order 42', description: /shipped/ })}`);
});
```

### Expected behavior

```
getByRole('button', { name: /Delete/i, description: 'Removes the item' })
getByRole('row', { name: 'Order 42', description: /shipped/ })
```

### Actual behavior

```
internal:role=button[name=/Delete/i][description="Removes the item"i]
internal:role=row[name="Order 42"i][description=/shipped/]
```

The locator still matches, but this raw selector is what shows up in the `Locator:` line of expect errors and in `waiting for` call logs. Python, Java and .NET print it raw too. Two regexes or two strings print fine.

### Additional context

It comes from the exactness check added in #41035. A regex is parsed as case sensitive, so next to a string that isn't exact it counts as a conflict. I'd be happy to send a fix.

### Environment

macOS, Node 25.6.1, Playwright main at ebf3a87

Start with the exactness check introduced in #41035 and the getByRole locator serialization exercised by the reproduction. Compare the output for mixed regex and string name or description values with the expected public getByRole strings, then add regression coverage showing the raw internal selector is no longer printed.

Written by the indexing model from the issue text.