Output test coverage from unit tests action

[JAORMX]

Summary

This converges the test and the cover actions into one. Having two is
wasteful and the benefit unclear.

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

Pull Request Test Coverage Report for Build 11341714732

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.6%) to 54.024%

---

Files with Coverage Reduction	New Missed Lines	%
internal/authz/authz.go	1	69.85%

Totals
Change from base Build 11341699177:	0.6%
Covered Lines:	14800
Relevant Lines:	27395

---

💛 - Coveralls