Added support for client certificates

[Samat-Imamov]

Issue: #1030

why

Allowing authentication using provided client certificates during local runs.

what changed

Additional configuration value 'clientCertificates' that's being passed during Playwright context creation.

test plan

This is additional support for already existing Playwright feature so Playwright team's internal test for this feature should be enough. But to test locally, provide client certificate config according to this API - https://playwright.dev/docs/api/class-browser#browser-new-context-option-client-certificates - and authenticate to whichever service that certificate belongs to.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 821688e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[greptile-apps]

Greptile Summary

This PR adds client certificate support to enable authentication using provided client certificates during local browser runs. The implementation extends the existing LocalBrowserLaunchOptions interface with a clientCertificates property that gets passed through to Playwright's context creation, leveraging Playwright's built-in client certificate authentication feature.

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it adds optional client certificate support
• Score reflects straightforward implementation that extends existing configuration pattern and leverages proven Playwright functionality without breaking changes
• No files require special attention - this is a simple additive feature

_{2 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}