Extend HUB CI timeout from 90 min to 240 min

[glenn-jocher]

@kalenmike @sergiuwaxmann @AyushExel I saw that since the CI timed-out after 90 min we did not get a Slack error message, so I've extended the timeout to 240 min, which should be long enough to fail all export formats and then submit an error message to Slack.

copilot:all

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Reduced CI timeout and expanded failure notifications for the Ultralytics repository.

📊 Key Changes

• 🕒 CI timeout has been decreased from 90 minutes to 60 minutes.
• 🔔 Failure notification condition updated; now includes both failure() and cancelled() events for certain triggers.

🎯 Purpose & Impact

• 🚀 Decreasing the timeout is likely to make the CI pipeline more efficient by freeing up resources sooner for cases where jobs may not need the full 90 minutes.
• 📢 Updating the notification condition to include cancelled() events ensures that maintainers are informed not just about process failures, but also about any cancellations which could highlight issues with the CI workflow or manual interventions.
• 👁️‍🗨️ Improving automation and monitoring can potentially lead to quicker identification and resolution of issues, streamlining the development process for all contributors.