feat(django): Add span around Task.enqueue

[sentrivana]

Description

Add a queue.submit.django span when a Task in enqueued via Django.

Issues

Closes#5201
Closes PY-2006

Reminders

• Please add tests to validate your changes, and lint your code using tox -e linters.
• Add GH Issue ID & Linear ID (if applicable)
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

[linear]

PY-2006 Check that Django 6.0 is fully instrumented

[codecov]

Codecov Report

❌ Patch coverage is 92.30769% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.26%. Comparing base (46676a9) to head (176a660).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
sentry_sdk/integrations/django/tasks.py	91.30%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@ Coverage Diff @@## master #5209 +/- ## ========================================== + Coverage 82.87% 84.26% +1.39%  ========================================== Files 181 182 +1 Lines 18459 18489 +30 Branches 3287 3290 +3 ========================================== + Hits 15297 15580 +283 + Misses 2141 1895 -246 + Partials 1021 1014 -7 

Files with missing lines	Coverage Δ
sentry_sdk/consts.py	99.41% <100.00%> (+<0.01%)	⬆️
sentry_sdk/integrations/django/__init__.py	85.27% <100.00%> (+0.07%)	⬆️
sentry_sdk/integrations/django/tasks.py	91.30% <91.30%> (ø)

... and 16 files with indirect coverage changes

[cursor]

Bug: Queue span uses HTTP origin instead of queue origin

The queue.submit.django span uses DjangoIntegration.origin which is "auto.http.django", but queue operations in other integrations (arq, celery, huey) consistently use "auto.queue.{name}" as the origin. This causes the span to be incorrectly categorized as an HTTP operation rather than a queue operation, which is inconsistent with other queue integrations and may affect how Sentry analyzes and displays queue-related telemetry data.

[alexander-alderman-webb]

I think this is a valid point @sentrivana.

[sentrivana]

IDK if origin is actually used anywhere on the server, but the OG idea behind the field is just to be able to determine which integration the span is coming from, nothing more.

When someone actually uses Celery/some other queuing library as a backend for django.tasks, those will have their own origin.

[alexander-alderman-webb]

LGTM, see the comments before merging 🙏

[alexander-alderman-webb]

nitpick: would it make more sense to use __qualname__ here?

Suggested change

	getattr(self.func, "__name__", repr(self.func)) or"<unknown Django task>"
	getattr(self.func, "__qualname__", repr(self.func)) or"<unknown Django task>"

[alexander-alderman-webb]

I think this is a valid point @sentrivana.

[sentrivana]

It's not public, but it's def there and pretty integral to the whole tasks feature, so I don't expect it to disappear.