fix(tracing): apiName determination with event listeners

[mxschmitt]

The PR fixes an issue with incorrect apiName determination in tracing when using event listeners. Here's what was happening:

When using sync event listeners, the stack trace would include internal implementation details from the _impl_to_api_mapping module, which acts as glue between user code and internal code. We expect no other function between the implementation and the user call-side. This caused the API name to be incorrectly determined since these internal frames were being included in the stack analysis.

The key changes:

• Added filtering to skip stack frames from _impl_to_api_mapping when extracting stack trace information
• Added test cases for both sync and async event listeners to verify correct API name determination

The async case worked correctly because async event listeners only schedule asyncio.Tasks without maintaining the full stack trace.

Test Plan:

• Added new test cases test_should_correctly_determine_sync_apiname for both sync and async implementations
• Tests verify correct API action sequence in traces when using event listeners
• Tested with response handlers making API calls like all_headers() and text()

Fixes #2650