Making Deployment flexible

[thielpa]

User story:
As a user I want to be not locked in deploying only via Helios, but if Helios is down also deploy manually.

Demo:

1. Deployment via Helios:
   a) Click on Artemis
   b) Click deploy
   c) Go to environment url -> see its deployed
2. Deployment via Github:
   a) Go to GitHub Action
   b) Click manually deploy
   c) Go to environment url -> see its deployed

⚠ Risks:

• Someone can bypass the locking mechanism via manual deployment
• Someone can deploy to prod without security checks

[egekocabas]

Sent a message to Timor and waiting his opinion about only using workflow_dispatch without any deployment_protection_rules.

[egekocabas]

• Artemis PR updated and its ready for review -> Development: Add Helios-based deployment workflow for test servers and reusable build logic Artemis#10109 (comment)
• I also created a PR in Helios where i will make the required changes but right now waiting a feedback on Artemis PR since is there will be a change in Artemis PR then this means we will also make changes in Helios -> feat: Align test server deployment with Artemis workflow changes #273
• Send another message to Timor in slack helios channel