Add E2E Tests and Code Coverage Infrastructure

[defauth98]

Implemented a comprehensive E2E test suite using Playwright and configured a code coverage infrastructure for the Proffy web application.

Key features:

• E2E Test Suite: Covered all mandatory pages including Login, SignIn, ForgetPassword, Landing, ListClasses, TeacherForm, and UserPerfil.
• Backend Mocking: Used Playwright's route API to mock backend responses, ensuring the test suite is self-contained and stable.
• Code Coverage: Integrated Istanbul instrumentation via @craco/craco to collect real code coverage from E2E runs without ejecting from Create React App.
• Reporting: Automated the collection and merging of coverage data to generate HTML, LCOV, JSON, and Text Summary reports.
• CI/CD Ready: Configured scripts and Playwright settings to be compatible with automated pipelines.

Current Coverage Summary:

• Statements: ~68%
• Functions: ~75%
• Branches: ~51%

---

PR created automatically by Jules for task 5331052816821470944 started by @defauth98

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
33991011	Triggered	Generic High Entropy Secret	995a55a	server/Insomnia_2020-10-27.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}