Evaluate QA GitHub Actions for Cloudbeat handover

## Summary
Review the Cloudbeat GitHub Actions that currently support the QA process and map which actions are still needed by the contextual team as part of the handover.

A specific decision point is whether the existing environment-creation flow should remain in the GitHub Action workflow, or whether it should be replaced with a new flow built on currently supported tooling such as the `oblt` CLI.

## Scope
- Inventory the Cloudbeat QA-related GitHub Actions and the steps they perform today.
- Identify which actions should be kept, removed, or replaced.
- If replacement is preferred, outline the recommended approach and supporting tooling.

## Acceptance Criteria

- [x] A documented mapping exists for the Cloudbeat QA GitHub Action steps in use today.
- [x] Each action/step is categorized as keep, remove, or replace for the contextual team.
- [x] There is a recommendation on whether to continue using the current environment-creation flow.
- [ ] If a new approach is preferred, the issue captures the proposed replacement path and next implementation steps.