Use annotation for coverage report

[numbata]

Changes a way of how action comment the warnings to annotations-via-console. Writing coverage annotations directly to the console avoids the API call, which in turn lets the workflow run with the default GITHUB_TOKEN (no repository write permission).

[github-actions]

Memory Profile Report

Summary

Metric	Value
Iterations	5
API Endpoints	18
Avg Allocated	1.73 MB
Avg Retained	188.88 KB
Retained Trend	20.94%
Memory Stable	No
Potential Leak	No

Iteration Details

#	Allocated	Retained	Objects
1	1.73 MB	132.66 KB	22685
2	1.73 MB	202.94 KB	22685
3	1.73 MB	202.94 KB	22685
4	1.73 MB	202.94 KB	22685
5	1.73 MB	202.94 KB	22685

Top Memory Allocations (by location)

#	Avg Memory	Location
1	120.90 KB	lib/grape_oas/api_model_builders/concerns/oas_utilities.rb:18
2	119.53 KB	...grape_oas/introspectors/entity_introspector_support/exposure_processor.rb:256
3	84.84 KB	lib/grape_oas/api_model/schema.rb:26
4	84.84 KB	lib/grape_oas/api_model/schema.rb:32
5	51.25 KB	vendor/bundle/ruby/3.4.0/gems/securerandom-0.4.1/lib/securerandom.rb:71
6	49.22 KB	lib/grape_oas/introspectors/entity_introspector.rb:97
7	40.62 KB	lib/grape_oas/api_model/schema.rb:43
8	32.93 KB	vendor/bundle/ruby/3.4.0/gems/dry-logic-1.6.0/lib/dry/logic/rule.rb:94

---

_{Generated by Memory Profile workflow • Commit: 819a01b}

[numbata]

Why this specific commit: See the discussion in ggilder/codecoverage#20. This commit changes a way of how action comment the warnings to annotations-via-console. Writing coverage annotations directly to the console avoids the API call, which in turn lets the workflow run with the default GITHUB_TOKEN (no repository write permission)

Current GitHub annotation limits

• 10 warnings + 10 errors per step
• 50 annotations per job (sum of all steps)
• 50 “run” annotations (system-generated)

If we ever need more than those limits, we can pin the action to a tag that re-enables the API path—at the cost of requiring the checks: write permission again.