fix: track deployment workflow runs

[mertilginoglu]

Motivation

Helios deployments were not reliably linked to the GitHub workflow run that actually executed the deployment. That made it harder to keep deployment status in sync, to resolve cancellations and job-status lookups against the correct repository, and to match GitHub deployment events back to the active Helios deployment when branch names differed from the workflow branch.

Description

• store workflow run metadata returned by the GitHub workflow dispatch endpoint on HeliosDeployment
• request workflow run details during dispatch and add a dedicated WorkflowDispatchResult model
• refresh redeploy decisions from the persisted workflow run status instead of relying only on the last stored deployment status
• resolve workflow cancellation and job-status lookups through the deployment linked to the workflow run before falling back to repository context
• improve GitHub deployment synchronization by preferring active unresolved Helios deployments and matching by SHA when the workflow branch differs from the deployed branch
• add server-side tests for workflow dispatch result handling, deployment status refresh, and deployment sync matching

Testing Instructions

Prerequisites:

• GitHub Account without having any additional access-rights (e.g. admin, owner)
• A repository/environment setup in Helios with a deployment workflow
• A branch and commit that can be deployed through the environment

Flow:

1. Log in to Helios as a Developer.
2. Start a deployment for an environment that uses a GitHub Actions deployment workflow.
3. Verify that the created Helios receives workflowId from GitHub and saves it to the deployment.

Checklist

General

• PR description explains the purpose and changes. (f.e. following the 'Conventional Commits') (https://www.conventionalcommits.org/en/v1.0.0/)
• Changes have been tested locally.

Server

• Code is performant and follows best practices

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.10% (target: -1.00%)	✅ 30.84%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (d8b47d4)	8700	2971	34.15%
Head commit (b4b341d)	8772 (+72)	3004 (+33)	34.25% (+0.10%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#932)	107	33	30.84%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[meryemefe]

I tested locally, LGTM

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b4b341da96

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".