fix: Update span op for outgoing HTTP requests

[rhcarvalho]

We've established that incoming requests have op=http.server and outgoing requests have op=http.client.

Specification available at: https://develop.sentry.dev/sdk/features/#http-client-integrations
Last update: getsentry/develop#341

---

Note: this has the unfortunate potential to break anything relying on the old op value. While the change is simple, some consideration needs to be taken.

[AbhiPrasad]

This will have product ramifications. Pinging @getsentry/visibility to get their thoughts.

[github-actions]

size-limit report

Path	Size
@sentry/browser - CDN Bundle (gzipped)	21.46 KB (0%)
@sentry/browser - Webpack	22.47 KB (0%)
@sentry/react - Webpack	22.5 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped)	28.97 KB (+0.02% 🔺)

[kamilogorek]

Nice, our tests caught something :D

[rhcarvalho]

Nice, our tests caught something :D

Haha, yeah, it was a .js file (nextjs integration tests), excluded from my search filter :)

[k-fish]

This will have product ramifications. Pinging @getsentry/visibility to get their thoughts.

Do you mean operations breakdown?

Ops breakdown uses http with startsWith in relay so it shouldn't be affect if we are just adding more to the op.

http
https://github.com/getsentry/sentry/blob/809b7fe54c6f06cc1e4c503cf83ded896472a011/src/sentry/projectoptions/defaults.py#L74

startsWith
https://github.com/getsentry/relay/blob/9fd1a4310ea7f18a09df9f3a772339a546d6e422/relay-general/src/store/normalize/breakdowns.rs#L148

[dashed]

@k-fish @rhcarvalho @AbhiPrasad tldr: this has no product ramifications; this rename will match cleanly on the operation names breakdown feature. In other words, http.client and http.server will group to http spans on the product.

[AbhiPrasad]

Perfect, think we are good to go then.