fix(profiling): export lock acquire/release call location and variable name [backport 2.10]

[taegyunkim]

Manual backport of #9615 to 2.10

We used to export ":<line_number>" for the name of a lock. Whenever lock is initialized, we traverse the stack frame to populate these. However, we can't get the variable name of the lock as we haven't yet fully initialized and assigned it to a variable.

Now we traverse the frame whenever _acquire/_release is called to get the caller information. Also, when _acquire is called for the first time, we inspect local and global variables in the caller frame to find the name of this lock variable. With
DD_PROFILING_LOCK_NAME_INSPECT_DIR enabled, the lock profiler also inspects attributes of local and global variables to find the name of the lock. This behavior can be turned off with the flag.

Checklist

• Change(s) are motivated and described in the PR description
• Testing strategy is described if automated tests are not included in the PR
• Risks are described (performance impact, potential for breakage, maintainability)
• Change is maintainable (easy to change, telemetry, documentation)
• Library release note guidelines are followed or label changelog/no-changelog is set
• Documentation is included (in-code, generated user docs, public corp docs)
• Backport labels are set (if applicable)
• If this PR changes the public interface, I've notified @DataDog/apm-tees.

Reviewer Checklist

• Title is accurate
• All changes are related to the pull request's stated goal
• Description motivates each change
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Change is maintainable (easy to change, telemetry, documentation)
• Release note makes sense to a user of the library
• Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance
  policy

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: backport-9615-to-2.10
Commit report: 1197bdc
Test service: dd-trace-py

✅ 0 Failed, 391 Passed, 1199 Skipped, 33m 24.37s Total duration (47m 23.42s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-08-02 13:05:44

Comparing candidate commit 88f94aa in PR branch backport-9615-to-2.10 with baseline commit c4d6251 in branch 2.10.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 221 metrics, 9 unstable metrics.