chore: remove --save-trace codegen option

[pavelfeldman]

No description provided.

[yury-s]

I'd keep it for now. There is no better alternative for the scenario that the option was introduced for.

[github-actions]

Test results for "tests 1"

7 flaky

⚠️ [firefox-page] › tests/page/page-evaluate.spec.ts:403:3 › should throw for too deep reference chain @firefox-ubuntu-22.04-node18
⚠️ [installation tests] › tests/playwright-electron-should-work.spec.ts:44:5 › should work when wrapped inside @playwright/test and trace is enabled @package-installations-macos-latest
⚠️ [chromium-library] › tests/library/inspector/cli-codegen-python-async.spec.ts:26:5 › should print the correct imports and context options @ubuntu-20.04-chromium-tip-of-tree
⚠️ [webkit-library] › tests/library/inspector/cli-codegen-1.spec.ts:795:7 › cli codegen › should middle click @webkit-ubuntu-22.04-node18
⚠️ [webkit-library] › tests/library/proxy.spec.ts:238:3 › should use socks proxy in second page @webkit-ubuntu-22.04-node18
⚠️ [webkit-library] › tests/library/trace-viewer.spec.ts:366:1 › should filter network requests by resource type @webkit-ubuntu-22.04-node18
⚠️ [webkit-library] › tests/library/tracing.spec.ts:506:5 › should work with multiple chunks @webkit-ubuntu-22.04-node18

37596 passed, 648 skipped
✔️✔️✔️

Merge workflow run.

[aswathpp97]

Hi, why is this --save-trace option removed from the latest version, and what is the alternative to use?