Issue Description
In Sentry, there's a section for Sidekiq exceptions that records the configuration. It looks like in Sidekiq 7, this is not serialized/inspected in a way that actually conveys any useful information.

Reproduction Steps
Record an exception with 5.7.0 and observe the "Sidekiq" section of the exception.
Expected Behavior
I would expect this section to either not exist in the report or to show Sidekiq settings such as queues, concurrency, timeout, etc.
Actual Behavior
_config is printed as something like #<Sidekiq::Config:0x00007f447c676368>
Ruby Version
3.1.3
SDK Version
5.7.0
Integration and Its Version
sentry-sidekiq
Sentry Config
No response
Issue Description
In Sentry, there's a section for Sidekiq exceptions that records the configuration. It looks like in Sidekiq 7, this is not serialized/inspected in a way that actually conveys any useful information.
Reproduction Steps
Record an exception with 5.7.0 and observe the "Sidekiq" section of the exception.
Expected Behavior
I would expect this section to either not exist in the report or to show Sidekiq settings such as queues, concurrency, timeout, etc.
Actual Behavior
_configis printed as something like#<Sidekiq::Config:0x00007f447c676368>Ruby Version
3.1.3
SDK Version
5.7.0
Integration and Its Version
sentry-sidekiq
Sentry Config
No response