Deactivate nightly master pipeline

Ref: #3662 (closed)

Problem

Currently we have daily master pipeline that executes 1900+ jobs including all unit/integration tests and db configs tests. The pipeline takes 4+hours but provides limited value or oversights.

• Redundant coverage: Most jobs in this pipeline are already executed in other daily/hourly pipelines and specific MR pipelines (e.g., database changes)
• No active monitoring: Test job failures are not being actively monitored or triaged by the stage groups
• Disconnected from release/deploy cycle: The pipeline is outside of our release/deployment cycle and doesn't provide timely feedbacks to development team for decision making.

Orchestrated tests consideration: Some orchestrated tests currently run exclusively in this pipeline 👇

Screenshot

We'd want to evaluate these jobs to see if they provide unique values, and if so, where they should be repositioned in the development workflow to deliver more timely feedback.

Proposal

Deactivate the daily master pipeline as part of our broader test strategy optimization efforts.

Next Steps

• Disable the pipeline and communicate with DevEx DRIs
• Monitor for 2 - 4 weeks for any quality impacts or test gaps, and use this issue to track any action items
• Decide what we want to do with the orchestrated tests - Move orchestrated tests executed only in nightl... (#3714 - closed)