CI: Increase default TIMEOUT used during rolling upgrades

What does this MR do and why?

During scheduled pipelines and MR pipeline flagged with ci-featuretest-rolling-upgrade , our CI deployments are performing a rolling upgrade so we need to defined bigger timeout. Initially theses timeout were designed with CAPO usecases in mind, for CAPM3 they can be too short. This MR increase the timeout both for CAPO & CAPM3 in theses cases.

If we noticed that for CAPO it lead to jobs taking too much time to failed we could override in the scheduled pipelines definition.

When this MR will be merged, we should clean the override actually done at scheduled pipelines definition for the pure capm3 deployments