Ok Http Retry Tracking using the EventListner API?

### Description

Hello Team, I have a question about how we are tracking the network metrics using the OkHttp EventListenerAPI here - https://github.com/getsentry/sentry-java/blob/main/sentry-okhttp/src/main/java/io/sentry/okhttp/SentryOkHttpEventListener.kt

From my understanding, with the current implementation, if a request is retried, the event listener only captures metrics for the latest attempt and does not track metrics for each retry separately. So, if there are three requests (one original and two retries), we only see metrics for the last one. I understand that some metrics, like CONNECT, SSL, and DNS, would only be recorded for the initial request since OkHttp reuses the connection. However, other metrics could still be relevant for retries.

Was there a specific reason for implementing it this way?

Looking forward to your insights!

Start with sentry-okhttp/src/main/java/io/sentry/okhttp/SentryOkHttpEventListener.kt and the OkHttp EventListener API to understand how attempts are observed. The issue does not define a requested change or acceptance criteria; clarify whether retry attempts should be tracked separately and what completion means before implementation.

Escrita pelo modelo de indexação a partir do texto da issue.