Fix another edge case in Azure callbacks handling

[pulkomandy]

Checklist

• [x] I have read the [contribution guidelines] (https://github.com/Azure/azure-iot-sdk-c/blob/main/.github/CONTRIBUTING.md).
• [x] I added or modified the existing tests to cover the change (we do not allow our test coverage to go down).
• If this is a modification that impacts the behavior of a public API
  • [ ] I edited the corresponding document in the devdoc folder and added or modified requirements.
• I submitted this PR against the correct branch:
  • [x] This pull-request is submitted against the main branch.
  • [x] I have merged the latest main branch prior to submission and re-merged as needed after I took any feedback.
  • [x] I have squashed my changes into one with a clear description of the change.

Reference/Link to the issue solved with this PR (if any)

2569

Description of the problem

The previous fix for bug 2569 missed an edge case where the upload is succesful but the notification is not. In that case, there would be a success callback followed by an error one, which is not expected (the success callback should be the last one).

Description of the solution

Delay the success callback until the return of the upload function, in case errors happen in the late stage of the upload to blob.

[pulkomandy]

@microsoft-github-policy-service agree company="Viveris Technologies"

[ewertons]

This PR has been replaced by https://github.com/Azure/azure-iot-sdk-c/pull/2615 Thanks, Azure IoT SDKs Team.