fix(e2e): move playwright-go to mxschmitt path @v0.6100.0 (dead CDN)

[CybotTM]

Problem

The CI / E2E Tests job has failed on main for 3 weeks on the unchanged commit. playwright-go v0.5700.1 downloads its driver from the retired Azure/Edgio mirrors, which now 404:

install playwright: could not install driver: got non 200 status code: 404
  https://playwright.azureedge.net/builds/driver/playwright-1.57.0-linux.zip
  https://playwright-akamai.azureedge.net/...
  https://playwright-verizon.azureedge.net/...
FAIL github.com/netresearch/ldap-manager/internal/e2e

Fix

Upstream reverted the canonical module path back to github.com/mxschmitt/playwright-go (both mxschmitt/* and playwright-community/* repos declare module github.com/mxschmitt/playwright-go at the latest release). v0.6100.0 fetches the driver from registry.npmjs.org + nodejs.org/dist instead of the dead CDN.

• v0.6000.0 (community path) still hardcodes azureedge → does not fix it.
• The playwright-community v0.6100.0 tag ships a mismatched go.mod module path → not go get-able under that path.

So this switches the import path (11 files, all in internal/e2e/) and pins v0.6100.0.

Verification

• go build -tags e2e ./... → passes (no breaking API changes).
• go mod tidy → stable, no stale entries.
• playwright install chromium on a clean driver cache → exit 0 (driver now downloads; the old version exits 1 with the 404 above).

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
gomod/github.com/mxschmitt/playwright-go	0.6100.0	🟢 5.2	Details Check Score Reason Maintained 🟢 10 30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10 Code-Review ⚠️ 1 Found 5/30 approved changesets -- score normalized to 1 Packaging ⚠️ -1 packaging workflow not detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Binary-Artifacts 🟢 9 binaries present in source code CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md Signed-Releases ⚠️ -1 no releases found License 🟢 10 license file detected Pinned-Dependencies ⚠️ 2 dependency not pinned by hash detected -- score normalized to 2 Security-Policy 🟢 10 security policy file detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0

Scanned Files

• go.mod

[github-actions]

Automated approval for maintainer PR

All automated quality gates passed. See SECURITY_CONTROLS.md for compensating controls.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

⚠️ Mutation Testing Results

Mutation Score: 0% (threshold: 60%)

⚠️ Score is below threshold. Consider improving test coverage or test quality.

What is mutation testing?

Mutation testing measures test quality by introducing small changes (mutations) to the code and checking if tests detect them. A higher score means better test effectiveness.

• Killed mutants: Tests caught the mutation (good!)
• Survived mutants: Tests missed the mutation (needs improvement)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.94%. Comparing base (e1d0e09) to head (344b9d7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #623   +/-   ##
=======================================
  Coverage   69.94%   69.94%           
=======================================
  Files          34       34           
  Lines        3437     3437           
=======================================
  Hits         2404     2404           
  Misses        873      873           
  Partials      160      160           

Flag	Coverage Δ
e2e	58.99% <ø> (ø)
unittests	70.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[CybotTM]

Duplicate of #621 (same playwright-go module-rename fix, opened 2026-07-15). I opened this without checking for the existing PR — closing in favor of #621. Both are blocked on the repo's merge-queue + code_scanning ruleset deadlock (a required CodeQL result + a merge_group-only container check), which needs a repo-config fix before either can merge.