Repeated leaked connections on `delete` by version and `permanentDelete`

Describe the bug

We're getting this error very consistently when trying to permantently delete a drive item via API:

WARNING: A connection to https://graph.microsoft.com/ was leaked. Did you forget to close a response body?
java.lang.Throwable: response.body().close()
	at okhttp3.internal.platform.Platform.getStackTraceForCloseable(Platform.kt:143)
	at okhttp3.internal.connection.Transmitter.callStart(Transmitter.kt:111)
	at okhttp3.RealCall.execute(RealCall.kt:63)
	at com.microsoft.kiota.http.OkHttpRequestAdapter.getHttpResponseMessage(OkHttpRequestAdapter.java:747)
	at com.microsoft.kiota.http.OkHttpRequestAdapter.sendPrimitive(OkHttpRequestAdapter.java:364)
	at com.microsoft.graph.drives.item.items.item.permanentdelete.PermanentDeleteRequestBuilder.post(PermanentDeleteRequestBuilder.java:53)
	at com.microsoft.graph.drives.item.items.item.permanentdelete.PermanentDeleteRequestBuilder.post(PermanentDeleteRequestBuilder.java:42)

Expected behavior

No leaked connections

How to reproduce

client.drives().byDriveId("...").items().byDriveItemId("root:/...:").permanentDelete().post()

SDK Version

6.30.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

</details>


### Configuration

_No response_

### Other information

_No response_

从堆栈跟踪中显示的生成的 PermanentDeleteRequestBuilder.java 入口点开始，然后检查 OkHttpRequestAdapter 的响应处理。使用 permanentDelete().post() 在所述 SDK 场景中重现该调用，并跟踪响应正文的关闭过程。当请求完成且没有连接泄漏警告时，即表示完成。