Add dotenv environment variable support for Playwright tests

[krugazul]

Bug Report

Describe the bug
Playwright tests currently use hardcoded URLs and configuration. There is no support for environment variables, making it difficult to run tests in different environments or with custom settings.

To Reproduce
Run Playwright tests in the tests/ directory. The URLs and other config are hardcoded in the test files.

Expected behavior
Tests should use environment variables for configuration, such as the base URL, loaded via the dotenv package. This will allow flexible test configuration and easier CI integration.

Proposed Solution

• Add dotenv as a dev dependency.
• Load environment variables in Playwright test setup.
• Use variables (e.g., process.env.BASE_URL) in test files instead of hardcoded values.

Additional context
This will improve test portability and allow for different environments (local, staging, CI) without code changes.

---

This issue was generated by GitHub Copilot.

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Add Playwright testing with dotenv support by updating package.json to include @playwright/test, dotenv, and npm test scripts; add playwright.config.ts that loads .env and sets baseURL, browsers, CI-aware settings, and reporting; add .env.example with BASE_URL and credentials; add tests/ (example.spec.ts, plugin.spec.ts) and tests/README.md; and update .gitignore to exclude .env and Playwright artifacts.

• Add Playwright end-to-end testing support by creating playwright.config.ts, tests/ (example.spec.ts, plugin.spec.ts, README.md), and .env.example; update package.json to add Playwright scripts and devDependencies (@playwright/test, dotenv); and update .gitignore to ignore .env and Playwright test artifacts.

• ✅ Create PR with these edits
• 📋 Get copyable edits