Increase gh actions runner timeout for E2E tests completion

[Intenzi]

What?

Developer: Increases GH action runner timeout from 20 minutes to 30 minutes.

Why?

• Presently any new PR that aims to add more E2E tests will fail to run all tests.
• This is because the gh-actions runner takes a total of 19m 43s to completely run. (From last identified successful action run completion)
• As this is very close to the 20m timeout, new PR jobs will fail when adding additional E2E tests.
  • https://github.com/WordPress/ai/actions/runs/28453990663/job/84324826069?pr=739 (cancelled in 20m 16s)
  • https://github.com/WordPress/ai/actions/runs/28508379230/job/84502348297?pr=810 (cancelled in 20m 17s)

How?

Increased the timeout-minutes in test.yml to 30 minutes (from 20m).

• Identified root cause with the assistance of @yogeshbhutkar

Use of AI Tools

AI assistance: No

Testing Instructions

Rerun existing cancelled jobs in PRs such as #810

Changelog Entry

Developer - Increased test timeout from 20m to 30m.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.50%. Comparing base (4cbd972) to head (bc428fe).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #811   +/-   ##
==========================================
  Coverage      75.50%   75.50%           
  Complexity      2086     2086           
==========================================
  Files             99       99           
  Lines           8626     8626           
==========================================
  Hits            6513     6513           
  Misses          2113     2113           

Flag	Coverage Δ
unit	75.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Intenzi <intenzi@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.