Fix asyncpg spans

[sentrivana]

• Change span.set_data to span.set_attribute

• Change start_transactions in the tests to start_spans

• Stringify db.params, db.paramstyle, db.cursor

• ❗ Change how adding query source works.
  Previously, we first let the DB span finish and then looked at its start and end timestamps to figure out if the query was slow enough to attach query data.

  With the switch to OTel, we can no longer put stuff on a finished span, meaning the slow query span still has to be alive when adding data to it. So instead of looking at the end timestamp of a finished span, we keep the span alive and instead look at current time at the point when the query is finished.

  This means the DB span will be longer than the actual query (since it now includes adding query data).

[codecov]

❌ 2925 Tests Failed:

Tests completed	Failed	Passed	Skipped
20066	2925	17141	4443

View the top 3 failed tests by shortest run time

tests.integrations.litestar.test_litestar test_middleware_partial_receive_send

Stack Traces | 0s run time

No failure message available

tests.integrations.litestar.test_litestar test_middleware_partial_receive_send

Stack Traces | 0s run time

No failure message available

tests.integrations.litestar.test_litestar test_span_origin

Stack Traces | 0s run time

No failure message available

To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard

[sentrivana]

This is the query source change from the PR description