Automated testing

[Aerilym]

No description provided.

[Copilot]

Pull Request Overview

This PR introduces automated testing utilities for a Playwright project and updates testing configurations to support new e2e test scenarios.

• Added utility functions in utils.ts for interacting with elements by test IDs.
• Introduced new test cases in test.spec.ts to validate page navigation, dialogs, and TOS acceptance.
• Updated project configuration files (playwright.config.ts and jest.config.js) along with a new type definition for test IDs.

Reviewed Changes

Copilot reviewed 6 out of 10 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/playwright/tests/utils.ts	New utility functions for clicking elements and TOS agreement with a potential naming inconsistency for the page parameter.
packages/playwright/tests/types/testing.ts	Added type union for DataTestId values used in testing.
packages/playwright/tests/test.spec.ts	New test specs to verify web page behavior.
packages/playwright/playwright.config.ts	New Playwright configuration for test execution.
packages/playwright/jest.config.js	Jest configuration extended from a shared base config.
packages/playwright/README.md	Basic readme added for package documentation.

Files not reviewed (4)

• packages/playwright/package.json: Language not supported
• packages/playwright/test-results/.last-run.json: Language not supported
• packages/playwright/tsconfig.json: Language not supported
• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (2)

packages/playwright/tests/utils.ts:6

• [nitpick] The parameter name 'window' is unconventional in Playwright tests (typically 'page'). Consider renaming it for consistency with the rest of the codebase.

  window: Page,

packages/playwright/tests/utils.ts:24

• [nitpick] The parameter 'window' could be renamed to 'page' to align with common Playwright conventions and improve readability, as seen in other parts of the code.

  window: Page,