fix: prevent reporting expected module restart errors to Sentry (#599)

[Hany-Almnaem]

Summary

This PR fixes #599 by ensuring we no longer report expected module restart errors (due to inactivity) to Sentry.

---

Changes

• Refactored maybeReportErrorToSentry() to support dependency injection for testability
• Ensured module inactivity errors are marked with reportToSentry: false
• Removed direct use of Sentry.captureException and used DI to allow isolated unit testing
• Added minimal unit tests for maybeReportErrorToSentry() using a spy
• Replaced frozen namespace usage (Sentry) with functional imports (captureException, withScope)
• Linted and confirmed formatting with Prettier

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	sinon@​20.0.0

View full report

[bajtos]

Thank you for the pull request, @Hany-Almnaem.

It is unfortunately no longer relevant, because we decided to remove the Sentry integration - see #765.