feat(workflows): add github env debug

[ReenigneArcher]

Description

This PR adds a callable workflow that can be easily included in our repo workflows without copy/pasting the same logic all the time.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Pull Request Overview

This PR introduces a reusable GitHub Actions workflow that dumps the full github context for debugging across forks and internal branches.

• Adds a callable workflow (workflow_call) for dumping the GitHub context.
• Triggers on pull request events targeting the default branch.
• Outputs the serialized github context to the build log.

Comments suppressed due to low confidence (3)

.github/workflows/__call-github-env.yml:12

• The workflow is configured to trigger on the master branch; if your repository’s default branch is main, consider updating this to match or using ${{ github.ref }} dynamically.

      - master

.github/workflows/__call-github-env.yml:24

• [nitpick] For consistency and readability, capitalize 'GitHub' in the step name (e.g., Dump GitHub context).

      - name: Dump github context

.github/workflows/__call-github-env.yml:1

• [nitpick] Consider adding usage instructions or linking to a central README so consumers know how to include this callable workflow in their own pipelines.

---

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud