feat: Add flag to capture exceptions on futures in concurrent integration

[alexander-alderman-webb]

Provide the option to record when an exception is set on a Future returned by ThreadPoolExecutor.submit(). These were previously thrown only when result() is called on the future. Otherwise the exception is only stored on the future, and does not detected by the ThreadingIntegration despite concurrent using threading under the hood.

Closes #2614

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
23729	1	23728	2305

View the top 1 failed test(s) by shortest run time

tests.profiler.test_continuous_profiler::test_continuous_profiler_auto_start_and_manual_stop[non-experiment-start_profiler/stop_profiler-gevent]

Stack Traces | 0.535s run time

tests/profiler/test_continuous_profiler.py:291: in test_continuous_profiler_auto_start_and_manual_stop
    assert_single_transaction_with_profile_chunks(envelopes, thread)
tests/profiler/test_continuous_profiler.py:147: in assert_single_transaction_with_profile_chunks
    assert len(items["profile_chunk"]) > 0
E   assert 0 > 0
E    +  where 0 = len([])

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

[cursor]

Bug: Exception Callback Fails Context and Cancellation Handling

The report_exceptions callback doesn't use the isolation_scope and current_scope forked at submission time, so captured exception events lack proper context. Also, future.exception() can raise CancelledError if the future was cancelled, causing the callback to fail.

 

[alexander-alderman-webb]

That seems valid at first sight, I'll see if I can reproduce first-hand before changing

[alexander-alderman-webb]

Need to revisit this to see if we want a dedicated FutureIntegration or to roll this into ThreadingIntegration.