Update DaprClientGrpcTest.java

[love12yadav]

Description
This PR fixes a bug in the getStateThenDelete test in DaprClientGrpcTest.

Problem:
The test previously called client.getState(...) for key2 and stored it as a Mono, but did not block it immediately. Then it deleted the state using deleteState(...) and blocked that operation, meaning the deletion happened before the earlier getState was actually executed.

Despite the state having been deleted, the test incorrectly expected that the delayed .block() on getState would return the original value — which is incorrect. In a reactive system, the delayed getState should reflect the current store contents, which no longer include the deleted key.

Fix Summary:
Delayed the .block() on getState for key2 until after the deleteState call was executed.

Updated the mock to simulate that the state is removed after deletion.

Changed the test to correctly assert that the state value is null after deletion.

This aligns the test with the correct reactive behavior of the Dapr Java SDK.

Issue reference
Fixes: #1408

@salaboy and @siri-varma.

[siri-varma]

@love12yadav Can you please look at the failing tests ?

[artur-ciocanu]

@love12yadav thank you for your PR. It seems that you have a few white spaces changes and line breaks that adds noise.

Could you please make sure that you maintain the format and add just the changes that improves the test. Otherwise it is unclear which line is part of the improvement and which one is just formatting changes.

Thank you.