Verify spans are available for SQL transactions (converted to project)

This issue has been converted to a project [Verify spans are available for SQL transactions](https://linear.app/getsentry/project/verify-spans-are-available-for-sql-transactions-ca2db3c1776d)

---

In [HTTP Requests within SQL Transactions](https://linear.app/getsentry/project/sql-issue-detection-f94b4c4af773/overview#milestone-343cae13-49fe-4c07-95d6-cc28aefef58f) we would like to detect when HTTP client requests are being made during a SQL transaction however to do this correctly, we need to verify that we have spans available from each backend SDK for database transactions. Some SDKs are known to not send this information (ex: Django) so we'd like to audit where it is/isn't available and get it added where it's not available.

These are generally `BEGIN`, `COMMIT`, and `ROLLBACK` however if we are doing any special casing in SDKs there are nuances depending on the SQL dialect (ex: MySQL supports `START TRANSACTION` in addition to `BEGIN`). The linked milestone above has more details in the FAQ section.

Develop Doc: [https://develop.sentry.dev/sdk/telemetry/spans/sql-transactions/](https://develop.sentry.dev/sdk/telemetry/spans/sql-transactions/)

- [ ] create sub-issues for available DB integrations