Proposal: Switch from Retrofit2 to OkHttp3

When the SDK was first developed, we utilized Retrofit2 to improve implementation efficiency. However, nowadays, our API definitions are automatically generated from openapi YAML files, and the use of Retrofit2 has become less relevant.

Furthermore, with the lack of new versions of Retrofit2 since 2020, it might be a good time for us to consider alternatives. In my opinion, switching to OkHttp3 could bring about improvements in both code readability and maintainability.

I propose that we migrate from Retrofit2 to OkHttp3 for our HTTP client. I look forward to hearing the thoughts of others on this proposal. Thank you.

Start by reading the OpenAPI YAML definitions and the SDK's current Retrofit2 integration, then identify the generated API entry points and HTTP client usage. The proposal's intended outcome is to replace Retrofit2 with OkHttp3 while preserving the SDK's generated API behavior, but it does not name specific files or tests.

Written by the indexing model from the issue text.