Issue Description

It is not possible to have a single database connection for a process that then reports a sentry error asynchronously without opening an additional connection.

we have an RDS DB with many connections, but also a huge fleet of sidekiq workers that can scale up and down in the thousands. so doubling the connection count requirement is not currently possible.

Reproduction Steps

Create a single unicorn worker with a single DB connection that generates an error to report to sentry.

Expected Behavior

The process reports the error using a single DB connection.

Actual Behavior

The process requires two DB connections to report the error.

Ruby Version

2.6.5

SDK Version

5.3.0

Integration and Its Version

No response

Sentry Config

No response