Update e2e tests to support new configuration step order

[Nateowami]

This should have been updated in #3370, but was missed. Nothing is changed except the order of the steps.

---

This change is 

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.58%. Comparing base (46716f5) to head (b525f32).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3389   +/-   ##
=======================================
  Coverage   82.58%   82.58%           
=======================================
  Files         608      608           
  Lines       35958    35958           
  Branches     5864     5864           
=======================================
  Hits        29697    29697           
  Misses       5383     5383           
  Partials      878      878           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Copilot]

Pull Request Overview

This PR updates e2e tests to align with the new configuration step order that was introduced in PR #3370 but missed in the test files. The main change reorders the configuration steps in the draft generation workflow, moving reference project configuration before source project configuration.

• Reordered configuration steps in e2e test workflows to match new UI flow
• Commented out screenshot test code that was no longer needed
• Added pull_request trigger to GitHub workflow for better test coverage

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
localized-screenshots.ts	Reordered configuration steps and commented out login screenshot code
generate-draft.ts	Updated step order with clear comments for reference projects, source project, and training data
e2e-tests.yml	Added pull_request trigger to GitHub workflow

[Copilot]

The non-null assertion operator (!) is unsafe here. The viewportSize() method can return null, and forcing it with ! could cause a runtime error. Use null checking instead: const originalViewportSize = await page.viewportSize(); if (!originalViewportSize) throw new Error('Viewport size not available');

Suggested change

	const originalViewportSize = await page.viewportSize()!;
	const originalViewportSize = await page.viewportSize();
	if (!originalViewportSize) throw new Error('Viewport size not available');

[RaymondLuong3]

@RaymondLuong3 reviewed 2 of 3 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Nateowami)

[Nateowami]

Thank you @RaymondLuong3! Getting these merged so they actually start passing is going to be really helpful.