Support Issue Reporting Details in Swift Testing Parametrized tests

[andreichenchik]

Add support of proper issue reporting for parametrized tests in Swift Testing, fixing #402
Display of failed/passed messages to be fixed in #462

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.35%. Comparing base (77c60a6) to head (5ff4cd6).
⚠️ Report is 9 commits behind head on main.

Files with missing lines	Patch %	Lines
...rces/XcbeautifyLib/Renderers/OutputRendering.swift	0.00%	3 Missing ⚠️
Sources/XcbeautifyLib/Formatter.swift	50.00%	1 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (77c60a6) and HEAD (5ff4cd6). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (77c60a6)	HEAD (5ff4cd6)
	2	1

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #463      +/-   ##
==========================================
- Coverage   91.72%   86.35%   -5.38%     
==========================================
  Files          17       17              
  Lines        2127     2132       +5     
==========================================
- Hits         1951     1841     -110     
- Misses        176      291     +115     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[andreichenchik]

Sorry for multiple attempts, figuring out my way through the test cases and regexes.

[cpisciotta]

Thanks for your contribution @andreichenchik! Can you resolve the merge conflicts? Happy to help get this merged.