Add Test Reporter GitHub Action Plugin

[nselvara]

Fixes #27

[github-actions]

VUnit Test Results

130 tests  ±0   130 ✅ ±0   7s ⏱️ ±0s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit bf5ea50. ± Comparison against base commit 2e23cc6.

♻️ This comment has been updated with latest results.

[Copilot]

Pull request overview

This PR adds the dorny/test-reporter GitHub Action to the VUnit test workflow to provide enhanced test result reporting capabilities. This addresses issue #27.

Key Changes

• Added a new "Test Report" step using dorny/test-reporter@v2 to process VUnit test results
• Configured the action to parse test-reports/vunit_results.xml as JUnit XML format
• Set the step to run with !cancelled() condition and fail-on-error: false settings

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The name "VUnit Test Results" conflicts with the check_name used in the "Publish Test Results" step at line 78. Having duplicate names can cause confusion in the GitHub UI when viewing checks and test results. Consider using a more specific name like "Test Report Summary" or "Dorny Test Reporter" to differentiate it from the other test reporting mechanisms.

Suggested change

	name: VUnit Test Results
	name: VUnit Test Report Summary

[Copilot]

The new "Test Report" step uses a different conditional (if: ${{ !cancelled() }}) compared to the other test reporting steps in the workflow (lines 68, 75, 82) which use if: always(). This inconsistency means this step won't run if the "Run VUnit tests" step fails, while the other test reporting steps will. For consistent test result reporting regardless of test outcome, consider using if: always() instead.

Suggested change

	if: ${{ !cancelled() }}
	if: always()