fix: avoid using svc_src: m when service is among active integration defaults

[emmettbutler]

This change fixes an issue reported via Support in which svc_src is set to m in cases where service matches the _default_service of an active integration config. In such cases, the intended behavior is that it svc_src is equal to service.

The change also excludes the svc_src tag in cases where service == base_service.

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-05-01 19:16:57

Comparing candidate commit 00c94e4 in PR branch emmett.butler/sqlite3-snapshot-2 with baseline commit e5ec646 in branch main.

Found 0 performance improvements and 3 performance regressions! Performance is the same for 584 metrics, 4 unstable metrics.

scenario:iastaspects-stringio_aspect

• 🟥 execution_time [+543.156µs; +595.420µs] or [+14.042%; +15.394%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+83.315µs; +94.181µs] or [+19.416%; +21.948%]

scenario:telemetryaddmetric-1-count-metric-1-times

• 🟥 execution_time [+181.133ns; +209.018ns] or [+8.597%; +9.921%]

[brettlangdon]

other than the perf feedback this lgtm

I did not review all snapshots, scanning the rough shape of changes makes sense to me though why they are changing here

[brettlangdon]

question/suggestion about implementation, but otherwise lgtm

[rithikanarayan]

approved for serverless snapshots

[dubloom]

My main question is:
Why some integrations remove _dd.svc_src if service == base_service and others are setting _dd.svc_src == service.

Also why are we deleting django snapshots ?

[emmettbutler]

@dubloom django snapshots are deleted because the tests pass without them. Presumably this is because they are associated with tests that have been deleted. The cases where svc_src == service are because of inferred base service.

[wantsui]

LGTM! I left some small comments about some of the snapshots.