Describe the bug

I'm not sure when this started happening, maybe with the launch of the v4 SDK, but we have started seeing Sidekiq/ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper as the transaction name rather than the wrapped job class name for errors within Active Job/Sidekiq. It seems this is a new incarnation of #702.

To Reproduce

class FooJob < ApplicationJob
  def perform
    raise 'bar'
  end
end

Expected behavior

FooJob is used as the transaction name.

Actual behavior

Sidekiq/ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper is used as the transaction name.

Environment

• Ruby Version: 2.7.2
• SDK Version: 4.1.4
• Integration Versions:
• Rails 6.0.3.4
• Sidekiq 6.1.3

Sentry Config

Sentry.init do |config|
  # Send Sentry notifications asynchronously by default
  config.async = ->(event) { SentryJob.perform_later(event) }
end