Include the current attempt number in logs when retrying.

[minwoox]

Motivation: Currently, it is difficult to distinguish from a log if a request is being retried when a LoggingClient is added before a RetryingClient. Including the current attempt number in logs will help resolve this issue.

Modifications:

• Included the current attempt number in a RequestLog.

Result:

• The RequestLog now includes the current attempt number if the request is created from a retrying client.
• Close #5716
• (Deprecated)
  • ClientRequestContext.newDerivedContext(RequestId,HttpRequest,RpcRequest,Endpoint) is deprecated.
  • Use ClientRequestContext.newDerivedContext(RequestId,HttpRequest,RpcRequest,Endpoint,int).

[github-actions[bot]]

🔍 Build Scan® (commit: 6e797fd2bc56e069c91dc6e7f7110a791f4df4e7)

Job name	Status	Build Scan®
build-windows-latest-jdk-21	✅	https://ge.armeria.dev/s/bfxurznudoi7e
build-self-hosted-unsafe-jdk-8	✅	https://ge.armeria.dev/s/7jld6sqo47znw
build-self-hosted-unsafe-jdk-21-snapshot-blockhound	✅	https://ge.armeria.dev/s/e7qqxkkp5bhda
build-self-hosted-unsafe-jdk-17-min-java-17-coverage	✅	https://ge.armeria.dev/s/b4lpp3smrb6vs
build-self-hosted-unsafe-jdk-17-min-java-11	✅	https://ge.armeria.dev/s/kr4zqrkq3ktr6
build-self-hosted-unsafe-jdk-17-leak	✅	https://ge.armeria.dev/s/grbi6dszsdhbo
build-self-hosted-unsafe-jdk-11	✅	https://ge.armeria.dev/s/aqzbctchq6rw6
build-macos-12-jdk-21	✅	https://ge.armeria.dev/s/t4f6zdjm6mil4

[minwoox]

I didn't add a currentAttempt tag to the metric because the important aspect on the metric side is not the currentAttempt, but the totalAttempt, which we already handle. However, please let me know if you have a different opinion.