ci: adjust tpch1000 benchmark timeout

[everpcpc]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Wire matrix timeouts into cloud benchmark job

The new matrix entries add per-dataset timeout values (lines 140‑144), but the cloud job still hardcodes timeout-minutes: 20 for the benchmark step; the matrix value is never consumed. As a result tpch1000 runs still time out after 20 minutes instead of the intended 60, so the change in this commit has no effect on the longer benchmark.

Useful? React with 👍 / 👎.