feat(data-collection): Port redis, net:http, faraday and excon

[sl0thentr0py]

Makes url collection close to the table here. Note that we haven't renamed url to url.full yet, that will be done in the major.

Issues

• Resolves: feat(pii): Wire third-party breadcrumbs (Faraday, Net::HTTP, Excon, Redis) #3004
• Resolves: RUBY-192

[linear-code]

RUBY-192

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 10149e3. Configure here.}

[solnic]

Nice

[sentry]

Bug: The new format_query method incorrectly serializes nested hash query parameters, which is a regression from the previous build_nested_query implementation.
_{Severity: MEDIUM}

Suggested Fix

Update the format_query method to recursively handle nested hashes, converting them into the correct bracketed notation for URL query strings. This can be achieved by reintroducing logic similar to the removed build_nested_query function to restore the previous functionality.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: sentry-ruby/lib/sentry/utils/http_tracing.rb#L28-L32

Potential issue: The refactoring in `filter_query_params` introduced a new
`format_query` method that does not correctly handle nested hash structures for query
parameters. The previous implementation used `build_nested_query`, which supported this
functionality. If a user provides a nested hash as a query parameter (e.g., `{qux: {a:
1}}`), the new logic will incorrectly serialize it to a string like `"qux=[:a=>1]"`
instead of the expected `"qux[a]=1"`. This is a regression that can lead to malformed
HTTP requests for integrations like Excon when complex query parameters are used.