Reporter-tested: disable AvoidCorsURLLoaderRestartOnRedirect when preflighted redirects fail under route() on Chromium 156

Finding: If a credentialed fetch with a non-safelisted header (so it is preflighted) is redirected cross-origin and fails with TypeError: Failed to fetch only after any context.route() is registered, the reporter's tested workaround is to disable one Chromium feature. See https://github.com/microsoft/playwright/issues/43242. The reporter says playwright-core 1.64.0 with Chromium 156.0.8078.4 fails, while the same fetch without a route returns 200. 1.63.0 and earlier are reported unaffected. The redirected request ends net::ERR_ABORTED and never reaches the target server. The reporter's binary-swap table suggests the failure follows the Chromium build rather than the playwright-core version. Chrome for Testing 155.0.8043.0 passed, while 155.0.8047.0 through 157.0.8093.0 failed. The reporter also says raw CDP Fetch.enable with a non-matching pattern reproduces it. They suspect the Chromium change AvoidCorsURLLoaderRestartOnRedirect (https://chromium-review.googlesource.com/c/chromium/src/+/8278433). That cause is an unconfirmed reporter hypothesis. Workaround: the reporter says launching with --disable-features=AvoidCorsURLLoaderRestartOnRedirect makes the route case pass on 156. They note a user cannot add the flag without restating Playwright's whole --disable-features list, because the last switch wins. Applicability: this is unverified by KFA, and the side effects of disabling a Chromium feature are unknown. It is only reported on Chromium 156 with an unstated OS. Treat it as a test-environment mitigation. Status: the issue is closed as completed, but no PR, merged fix or release is linked. The v1.64.0 notes list Chromium 156.0.8078.4 and do not mention this problem (https://github.com/microsoft/playwright/releases/tag/v1.64.0). Fix status is UNKNOWN.