Support IAsyncEnumerable out of the box

Is your feature request related to a problem? Please describe.
This is not so much a problem, but difficult to implement as there is no abstracted concept of page (see https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/511). Every request has its own GetAsync(CancellationToken) and each page has its own NextPageRequest.

Describe the solution you'd like
I'd love to be able to do something like the following:

g.Groups["some id"]
  .Members
  .Request()
  .ToAsyncEnumerable(token);

This allows for processing in memory of what needs to be done, but the paging occurs without any intervention on command if needed.

Describe alternatives you've considered
I've implemented this manually for some of the collections I care about. For example:

public static IAsyncEnumerable<string> GetUserIds(this IGraphServiceClient g, CancellationToken token)
{
    return g.Groups["some id"]
          .Members
          .Request()
          .ToAsyncEnumerable(token)
          .Select(d => d.Id);
}

private static async IAsyncEnumerable<DirectoryObject> ToAsyncEnumerable(this IGroupMembersCollectionWithReferencesRequest request, [EnumeratorCancellation] CancellationToken token)
{
    if (request is null)
    {
        throw new ArgumentNullException(nameof(request));
    }

    do
    {
        var page = await request.GetAsync(token).ConfigureAwait(false);

        foreach (var item in page)
        {
            yield return item;
        }

        request = page.NextPageRequest;
    } while (request != null);
}

AB#7248

Start by tracing the collection request types that expose GetAsync(CancellationToken) and page.NextPageRequest, using the Members request in the issue as the entry point. Compare that flow with the provided ToAsyncEnumerable implementation and determine how the abstraction would apply across requests. Done means the shown request chain supports asynchronous iteration, automatic paging, and cancellation.