TiCDC: Increase pipeline timeouts and remove stage timeouts to prevent premature failures (#4102)
## Why This PR standardizes timeout configurations across all TiCDC integration test pipelines to ensure consistency and prevent premature job failures. The changes address scenarios where tests may run longer than previously allocated timeouts, especially in heavy-load or complex integration scenarios.
## Changes - **Increased overall pipeline timeout** from 80/100 minutes to a uniform 120 minutes across all pipelines - **Removed per-stage timeout configurations** for Checkout, Prepare, and Test stages to rely on the global pipeline timeout - Applied changes consistently to both standard and next-gen variants of: - Kafka integration tests (light/heavy) - MySQL integration tests (light/heavy) - Pulsar integration tests (light) - Storage integration tests (light/heavy)
## Impact - Provides more consistent timeout behavior across all test types - Reduces maintenance overhead by eliminating per-stage timeouts - Allows tests to complete without artificial time constraints while maintaining reasonable overall limits - Ensures both standard and next-gen pipelines have identical timeout configurations
