fix: prevent SystemExit(0) from being reported as Sentry error

[sentry]

The Sentry integration was incorrectly reporting SystemExit(0) as an error. SystemExit(0) (or SystemExit(None)) indicates a clean, successful exit, often raised by CLI frameworks like click. The _before_send hook in codecov_cli/opentelemetry.py has been updated to check for SystemExit with a success code (0 or None) in the hint['exc_info'] and return None to prevent these events from being sent to Sentry. This eliminates false-positive error reports for normal program termination.

Fixes CLI-G7

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
723	1	722	1

View the full list of 1 ❄️ flaky test(s)

api.temp.calculator.test_calculator::test_divide

Flake rate in main: 100.00% (Passed 0 times, Failed 1726 times)

Stack Traces | 0.001s run time

def
                test_divide():
                > assert Calculator.divide(1, 2) == 0.5
                E assert 1.0 == 0.5
                E + where 1.0 = <function Calculator.divide at 0x104c9eb90>(1, 2)
                E + where <function Calculator.divide at 0x104c9eb90> = Calculator.divide
                .../temp/calculator/test_calculator.py:30: AssertionError

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}