Expect the JDK and Vert.x clients to defer the request body

Records the behaviour those transports have once the azure-core fixes in
#50311 and #50312 ship. Until Storage picks up those versions the four
cases fail, which is the intended signal rather than a silent mismatch.

Netty stays as it is: the change there observes the interim response and
does not defer the body.

Author: gunjansingh-msft

sdk/storage/azure-storage-common/src/test/java/com/azure/storage/common/policy/ExpectContinueTests.java

@@ -416,8 +416,8 @@ static Stream<Arguments> transports() {
         Object[][] clients = {
             { "netty", "com.azure.core.http.netty.NettyAsyncHttpClientProvider", ContinueSupport.SENDS_HEADER_ONLY },
             { "okhttp", "com.azure.core.http.okhttp.OkHttpAsyncClientProvider", ContinueSupport.DEFERS_BODY },
-            { "jdk", "com.azure.core.http.jdk.httpclient.JdkHttpClientProvider", ContinueSupport.DROPS_HEADER },
-            { "vertx", "com.azure.core.http.vertx.VertxHttpClientProvider", ContinueSupport.SENDS_HEADER_ONLY } };
+            { "jdk", "com.azure.core.http.jdk.httpclient.JdkHttpClientProvider", ContinueSupport.DEFERS_BODY },
+            { "vertx", "com.azure.core.http.vertx.VertxHttpClientProvider", ContinueSupport.DEFERS_BODY } };
 
         return Stream.of(clients)
             .flatMap(client -> Stream.of(Arguments.of(client[0] + " sync", client[1], client[2], true),