Correctly categorize OTel Messaging Systems within Sentry

[saviogl]

Problem Statement

Sentry's Open Telemetry processor isn't correctly categorizing queues as per Sentry's expected definition, so any spans from ActiveJob, Sidekiq or the likes aren't showing up correctly or working as intended in the Sentry's platform.

The Sentry OTel processor should make sure that queues are being properly categorized so they work seamlessly with Sentry's platform

Solution Brainstorm

This PR implements that basic categorization layer building on top of the existing http/db logic.

[linear]

RUBY-87 Correctly categorize OTel Messaging Systems within Sentry