Increase CI build timeout from 450 to 600 minutes

[Croway]

Summary

Claude Code on behalf of Federico Mariani

• Increase the per-cell matrix build timeout from 450 minutes (7h30m) to 600 minutes (10h)
• The camel-4.14.x branch has had 3 consecutive ABORTs (builds [CAMEL-7462] Do not treat <HTTP/1.1 100 Continue> as final response #160-162) and camel-4.18.x also timed out on build Adding feature for stax reader to turn off xml namespace awareness #20
• With throttled matrix leg scheduling causing staggered starts, the slowest cells (ppc64le) need more headroom
• Build CAMEL-7447 Allow to stream the result of a database query #159 on camel-4.14.x shows a cell legitimately needed ~9.8h (estimated duration) to complete
• Builds run 1-2x/day, so 10h per cell fits comfortably in the daily cycle

Companion PRs for maintenance branches will follow.

Test plan

• CI Camel Core (Build and test) / main should no longer ABORT due to timeout
• Monitor next few builds to confirm completion within 600 minutes

🤖 Generated with Claude Code

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.