chore(profiling): use clang when --safety is set

[taegyunkim]

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, 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

[github-actions]

CODEOWNERS have been resolved as:

ddtrace/internal/datadog/profiling/build_standalone.sh                  @DataDog/profiling-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: taegyunkim/prof-10916-set-clang
Commit report: b69e22a
Test service: dd-trace-py

✅ 0 Failed, 1172 Passed, 296 Skipped, 5m 9.53s Total duration (16m 40.98s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-04 22:16:13

Comparing candidate commit b69e22a in PR branch taegyunkim/prof-10916-set-clang with baseline commit 79be26d in branch main.

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

scenario:iast_aspects-ospathbasename_aspect

• 🟩 execution_time [-485.282ns; -427.579ns] or [-13.258%; -11.682%]

scenario:iast_aspects-ospathdirname_aspect

• 🟩 execution_time [-588.757ns; -519.177ns] or [-14.184%; -12.507%]