feat: Allow checking statuscodes of batch response without parsing step body

[svrooij]

Fixes #621

Changes proposed in this pull request

• Expose GetResponsesStatusCodesAsync() for BatchResponseContentCollection and BatchResponseContent that allows checking the status codes without creating HttpResponseMessage for each step (that has to be disposed)
• Expose BatchRequestSteps for BatchRequestContentCollection so you can possibly fetch the failed steps to retry, for instance in case of some 429 results in the batch.
• extra constructor for BatchRequestContentCollection including the number of requests that may be combined. (At the moment you cannot combine more then 4 requests, when creating TodoTasks, all above 4 fail with 429.) This allows the user to use batching without having to manage smaller batches himself.

Other links

• https://svrooij.io/2023/03/03/batching-in-microsoft-graph/
• Demo code https://github.com/svrooij/msgraph-sdk-dotnet-batching/tree/main/sample/BatchClient
• Video demonstrating batching https://youtu.be/u9buNZxbSNk

@maisarissi I've made batching even better to also support getting the failing steps.

Microsoft Reviewers: Open in CodeFlow

[andrueastman]

Thanks again for this.

[maisarissi]

Thanks @svrooij again, for the proposed enhancements!

[svrooij]

@maisarissi does Microsoft also have a digital badge for "brilliant ideas"? And the mean reason for this latest PR was that we are faced with a limit of 4 requests when trying to modify TodoTasks. Where should I post about that issue?

[maisarissi]

Hey @svrooij . I'm not aware of such badge, but we are working on a new program related to SDKs :) Once the program is ready, we will communicate how things are going to work.
For the second question around TodoTasks, this is an API limitation, so I would say the best place to ask questions/features is the Microsoft Q&A: https://developer.microsoft.com/en-us/graph/support