ci: set timeout for e2e test and perf test

[tao12345666333]

What this PR does / why we need it:

As we have already set a timeout for ORG, any job that does not specify its timeout will default to using the global 10 minutes.

Company wide vars.GHA_DEFAULT_TIMEOUT = 10 minutes for our use-case repo wide vars.GHA_EXTENDED_TIMEOUT_MINUTES = 30 minutes was defined too

The e2e tests and performance tests running on GKE took more than 10 minutes, so I have set them to run for 30 minutes.

e2e-tests / gke (1.29.2, TestDeployAllInOnePostgresGatewayDiscovery$)
The job running on runner GitHub Actions 30 has exceeded the maximum execution time of 10 minutes.

ref: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/8517470363

Which issue this PR fixes:

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

- [ ] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.9%. Comparing base (d82716c) to head (a75def8).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #5786     +/-   ##
=======================================
- Coverage   73.9%   73.9%   -0.1%     
=======================================
  Files        176     176             
  Lines      18187   18187             
=======================================
- Hits       13456   13441     -15     
- Misses      3734    3749     +15     
  Partials     997     997             

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