ci: run the health score check with unit test workflow

[zimeg]

Summary

This PR runs the health score check with the unit test workflow which includes test coverage. We remove it from the integration tests to remove errors!

Follows #553

Preview

Before:

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.92%. Comparing base (bb7fade) to head (3f05cb3).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #559   +/-   ##
=======================================
  Coverage   95.92%   95.92%           
=======================================
  Files          14       14           
  Lines        2697     2697           
=======================================
  Hits         2587     2587           
  Misses        110      110           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zimeg]

Error: Integration tests from forked branches require maintainer approval.
Notice: Dispatch a test run at https://github.com/slackapi/slack-github-action/actions/workflows/integration.yml with ref 'pull/559/head'
Error: Process completed with exit code 1.

Changes of #553 remains well 🙏 ✨

[mwbrooks]

✅ Thanks for clarifying why it's removed yet runs! 😅

[zimeg]

@mwbrooks Thanks for a fast review for follow up fixes... It's difficult to debug this sometimes I find 🔍

I'm holding off on merging for the moment since the integration test status for the latest commit isn't updated from a dispatched run:

🔗 https://github.com/slackapi/slack-github-action/actions/runs/21928692109/job/63327444061

This is a recent change to our workflows in this project and I'm not sure immediate of a fix?