feat(azure_functions): add azure functions integration

[duncanpharvey]

This PR adds an integration for tracing the azure-functions package.

Additional Notes:

• This change only supports the v2 programming model. If there are enough requests for the v1 programming model we can add tracing in a future PR
• This change only supports tracing Http triggers. Tracing for other triggers will be added in future PRs
• Azure Functions package currently supports on Python versions 3.7 to 3.11 (no 3.12 support at the moment)
• azure-functions-core-tools package must be installed on the test runner for tests to work
  • Version pinned to 4.0.6280 due to some issues with the most recent versions
  • Package only supported on linux/amd64 architecture
• Builds off the integration work started by @gord02 in azure function integration #9726
• mariadb install was broken in the testrunner image so the install commands were updated in cc5b4a7
  • https://github.com/DataDog/dd-trace-py/actions/runs/12037495435/job/33561074357

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:

.riot/requirements/1337ee3.txt                                          @DataDog/apm-python
.riot/requirements/14b54db.txt                                          @DataDog/apm-python
.riot/requirements/1e62aea.txt                                          @DataDog/apm-python
.riot/requirements/73109d5.txt                                          @DataDog/apm-python
.riot/requirements/c2420c2.txt                                          @DataDog/apm-python
ddtrace/contrib/azure_functions/__init__.py                             @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/azure_functions/patch.py                                @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/contrib/internal/azure_functions/patch.py                       @DataDog/apm-core-python @DataDog/apm-idm-python
releasenotes/notes/feat-add-azure-functions-integration-108911bfe1e5f081.yaml  @DataDog/apm-python
tests/contrib/azure_functions/__init__.py                               @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/azure_function_app/function_app.py        @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/azure_function_app/host.json              @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/azure_function_app/local.settings.json    @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/test_azure_functions.py                   @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/azure_functions/test_azure_functions_patch.py             @DataDog/apm-core-python @DataDog/apm-idm-python
tests/snapshots/tests.contrib.azure_functions.test_azure_functions.test_azure_function.json  @DataDog/apm-python
.circleci/config.templ.yml                                              @DataDog/python-guild @DataDog/apm-core-python
.github/workflows/requirements-locks.yml                                @DataDog/python-guild @DataDog/apm-core-python
ddtrace/_monkey.py                                                      @DataDog/apm-core-python
ddtrace/ext/__init__.py                                                 @DataDog/apm-core-python @DataDog/apm-idm-python
docker-compose.yml                                                      @DataDog/apm-core-python
docker/Dockerfile                                                       @DataDog/apm-core-python
riotfile.py                                                             @DataDog/apm-python
tests/contrib/suitespec.yml                                             @DataDog/apm-core-python @DataDog/apm-idm-python

[datadog-datadog-prod-us1]

🔴 Code Quality Violation

silent exception (...read more)

Using the pass statement in an exception block ignores the exception. Exceptions should never be ignored. Instead, the user must add code to notify an exception occurred and attempt to handle it or recover from it.

The exception to this rule is the use of StopIteration or StopAsyncIteration when implementing a custom iterator (as those errors are used to acknowledge the end of a successful iteration).

    

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-11-27 16:23:15

Comparing candidate commit ac03dfd in PR branch duncan-harvey/azure-functions-integration with baseline commit d386312 in branch main.

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

scenario:iast_aspects-ospathsplitext_aspect

• 🟩 execution_time [-380.493ns; -329.263ns] or [-9.599%; -8.306%]