Development: Add Helios-based deployment workflow for test servers and reusable build logic

[egekocabas]

Checklist

General

• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

This PR adds a new action file testserver-deployment.yml to integrate with the Helios web application for test server deployments. The current label-based approach for triggering deployments will be replaced with this new workflow_dispatch based workflow.

Additionally, the build.yml workflow has been refactored to leverage a reusable workflow file (reusable-build.yml). This ensures consistency across workflows and simplifies future maintenance.

Description

Integration with Helios:

• The workflow is designed to work with the Helios application, which manages deployment requests.
• Helios handles locking of test servers and tracking deployment statuses.
• Helios stays in sync with GitHub through webhook events and periodic automatic syncing, ensuring all repository changes, such as new pull requests or branch updates, are accurately reflected in the Helios interface.

Reusable Build Workflow:

• Introduced reusable-build.yml to streamline build logic.
• The build.yml workflow has been updated to utilize this reusable workflow.
• The new testserver-deployment.yml workflow also utilizes the reusable workflow to handle deployment scenarios where builds are not found.

testserver-deployment.yml:

• Replaced label-based deployment triggers with a workflow-dispatch approach.
• Enabled deployments for both PRs and standalone branches.
• The label-based approach and other related logic will be removed in another PR, which will consolidate the contents of testserver-deployment.yml into testserver.yml.

Once this PR is merged, a follow-up PR will finalize the transition by moving the contents of testserver-deployment.yml into testserver.yml.

[egekocabas]

I have refactored the build.yml workflow and introduced a new reusable workflow file named reusable-build.yml. The updated build.yml now utilizes this reusable workflow. Additionally, the new deployment action (testserver-deployment.yml) also utilizes the reusable workflow for cases where we don't have the build.

Build workflow runs can be seen in this link.

Once this PR is merged, and the time comes to remove the current labeling logic, we can create another PR to move the contents of the testserver-deployment.yml into testserver.yml. This will finalize the transition to the new workflow structure.

Below are my testing outputs of this new testserver-deployment.yml:

Deployment from a Branch Without a PR

Workflow run: https://github.com/ls1intum/Artemis/actions/runs/12948960943
Branch Name: feature/test-helios-deployment-without-pr
Latest Commit SHA: 825fcb1
Built Docker Image Tag: branch-825fcb13375214f081de1c24958bd8e2c878cb00

Deployment from a Branch with a PR

When deploying from a branch with an open pull request, the workflow first verifies whether the latest build was successful. If the build is successful, the deployment proceeds. Otherwise, it fails.

Scenario 1: Build Still Running During Deployment (No Successful Build Found)

Workflow run: https://github.com/ls1intum/Artemis/actions/runs/12949128976
Branch Name: feature/testserver-deployments-with-helios
Latest Commit SHA (at that time): 8d9203d

Scenario 2: Successful Build Found

Workflow run: https://github.com/ls1intum/Artemis/actions/runs/12949268370
Branch Name: feature/testserver-deployments-with-helios
Latest Commit SHA (at that time): 8d9203d
Docker Image Tag: pr-10109

Note: The new workflow was tested by temporarily modifying the testserver.yml file to enable testing, as the workflow has not yet been merged into the default branch. (See add2b32 and 925a07f)

[ole-ve]

thanks for integrating the feedback. code looks good, really like the refactoring 👍