Allow writing to request stream for uploading content

Is your feature request related to a problem? Please describe.
Developers should be able to write to the request stream for uploads so they can generate content 'on the fly' without needing to buffer it in memory.

Describe the solution you'd like

An overload for ContentRequestBuilder.PutAsync which accepts a Stream -> () delegate . That is:

public async Task PutAsync(Action<Stream> write, Action<ContentRequestBuilderPutRequestConfiguration>? requestConfiguration = default) { }

Describe alternatives you've considered

Buffering content in-memory by using a MemoryStream and using the existing overload which accepts a Stream.

Additional context

There is an overload for PutAsync which accepts an existing stream which is useful for pull-based streaming where the content already exists. For example, from a file.

https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/7a2be45d2cf37f18a32cc9a60d0edf441fd23a08/src/Microsoft.Graph/Generated/Drives/Item/Items/Item/Content/ContentRequestBuilder.cs#L67-L79

The overload I'm proposing would be better for push-based streaming where you're generating content because it doesn't require you to hold it in-memory. For example:

1. constructing a zip archive from many files[^1]
2. serializing an object graph[^2]

I understand this SDK is generated. I'm guessing this kind of overload will either need to be supported by Kiota or added as an extension manually (if Kiota's interfaces actually allow access to the request stream.)

[^1]: Streaming Zip on ASP.NET Core
https://blog.stephencleary.com/2016/11/streaming-zip-on-aspnet-core.html
An article which demonstrates the push-pull distinction with zip archives and ASP.NET Core.
[^2]: Uploading data with HttpClient using a "push" model
https://thomaslevesque.com/2013/11/30/uploading-data-with-httpclient-using-a-push-model/
An article which demonstrates the push-pull distinction with serialization ASP.NET.

Start with the generated ContentRequestBuilder.PutAsync overloads in src/Microsoft.Graph/Generated/Drives/Item/Items/Item/Content/ContentRequestBuilder.cs. Inspect the Kiota interfaces and request-stream support to determine whether a write delegate can be exposed without buffering. Done means push-based content generation can upload through PutAsync while preserving the existing stream overload and request configuration.