ci: optimize suitspec for integrations

[mabdinur]

Currently we run all contrib tests when ddtrace/contrib/internal/* is modified.
For example updating ddtrace/contrib/internal/aiohttp/patch.py will run tests for postgres, flask, django, .....

This fix will optimize ci runs for integration level changes and free up gitlab runners 🤞

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:

tests/contrib/suitespec.yml                                             @DataDog/apm-core-python @DataDog/apm-idm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: munir/update-suitspec-contrib
Commit report: bd06e78
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1468 Skipped, 4m 33.12s Total duration (35m 40.91s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-07 23:07:13

Comparing candidate commit 22aca69 in PR branch munir/update-suitspec-contrib with baseline commit 122caa6 in branch main.

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