[BUG] CosmosSyncScripts null pointer exception in azure-cosmos 3.3.1

[allenhumphreys]

Describe the bug
When using CosmosSyncClient to execute a stored procedure, I'm receiving a null pointer exception from the SDK.

• It looks like the conversion from the underlying asynchronous response to the synchronous response should be doing a null check on storedProcedure() but it isn't.
  

  azure-sdk-for-java/sdk/cosmos/microsoft-azure-cosmos/src/main/java/com/azure/data/cosmos/sync/CosmosSyncScripts.java

  Line 298 in a044649

  return new CosmosSyncStoredProcedureResponse(response, getStoredProcedure(response.storedProcedure().id()));

• CosmosStoredProcedureResponse clearly documents that storedProcedure() can be null:
  

  azure-sdk-for-java/sdk/cosmos/microsoft-azure-cosmos/src/main/java/com/azure/data/cosmos/CosmosStoredProcedureResponse.java

  Line 37 in a044649

  * @return the stored procedure object or null

[kaerm]

@allenhumphreys thank you for reporting this - we will look into this

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagarathapar @srinathnarayanan @southpolesteve @shurd

[kushagraThapar]

This issue has been fixed on all SDK versions. Closing it