fix(github): don't fail CI when publishing test results is blocked

[7sharp9]

Dependabot and fork PRs get a read-only GitHub token that can't post test-result annotations, which was failing otherwise good builds.

If we make that step non-blocking so a permissions issue with a reporting step doesn't mask a good build. Fixes #425

[greptile-apps]

Limit reporting error suppression

continue-on-error applies to every invocation, including trusted pushes and same-repository pull requests where result publication is expected to work. A non-permission failure in this sole publication step will therefore leave annotations absent while CI remains green; limit suppression to the restricted Dependabot and fork contexts.

Knowledge Base Used: Build and Versioning

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Greptile Summary

Makes GitHub test-result publication non-blocking so permission failures on Dependabot and fork pull requests do not fail otherwise successful builds.

• Documents why restricted GITHUB_TOKEN contexts can prevent result publication.
• Allows the Linux test-result publishing step to fail without failing the job.

Confidence Score: 4/5

The PR is safe to merge, with a non-blocking concern that reporting failures are suppressed beyond the restricted-token contexts targeted by the change.

Test execution remains blocking, but unconditional error suppression allows the sole result-publication step to fail silently on trusted pushes and same-repository pull requests.

Files Needing Attention: .github/workflows/build.yml

Important Files Changed

Filename	Overview
.github/workflows/build.yml	Makes test-result publication non-blocking for all runs, which also suppresses reporting failures in trusted contexts.

_{Reviews (1): Last reviewed commit: "fix(github): don't fail CI when publishi..." | Re-trigger Greptile}