Consider retiring staging-orchestrated pipeline

A few biweeklies back a question was raised if staging-orchestrated could actually catch any issues that would not be caught by package-and-qa and staging runs.

It seems it heavily mimics the package-and-qa but using the staging instance. To reduce the load during pipeline-triage, we should consider retiring this type of run if it doesn't seem to provide any additional benefit.

Tasks:

• Remove related code from release-tools => MR
• Remove related code from infra-deployer => MR
• Remove from QA pipelines list => MR