BaseDeltaFunctionResponse breaking change introduced in 5.57.0

[tbithell]

Describe the bug

This code works in 5.56.1 and earlier, but breaks in 5.57 with - System.ArgumentException : The Parsable does not contain a collection property

`var pageIterator = PageIterator<DriveItem, BaseDeltaFunctionResponse>.CreatePageIterator(
appGraphServiceClient,
deltaGetResponse,
(driveItem) =>
{
allDriveItems.Add(driveItem);
return true;
},
(request) =>
{
deltaToken = DeltaHttpHelper.GetQueryStringValueFromURI(request.URI.AbsoluteUri, Utils.Constants.Token);
return request;
});

await pageIterator.IterateAsync();`

Expected behavior

My integration tests should continue to work properly as they did before upgraded to 5.57

How to reproduce

After getting DriveItem DeltaQuery results create a pageiterator with the following code in 5.56.1 and then again in 5.57. It will work fine in 5.56.1 and fail in 5.57

`var pageIterator = PageIterator<DriveItem, BaseDeltaFunctionResponse>.CreatePageIterator(
appGraphServiceClient,
deltaGetResponse,
(driveItem) =>
{
allDriveItems.Add(driveItem);
return true;
},
(request) =>
{
deltaToken = DeltaHttpHelper.GetQueryStringValueFromURI(request.URI.AbsoluteUri, Utils.Constants.Token);
return request;
});

await pageIterator.IterateAsync();`

SDK Version

5.57

Latest version known to work for scenario above?

5.56.1

Known Workarounds

None

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

[andrueastman]

Thanks for raising this @tbithell

I believe this is caused by this PR - microsoftgraph/msgraph-sdk-dotnet-core#903 that changes the reflection usage in library and looks like this affects BaseDeltaFunctionResponse model as it does not contain a Value property(it is added by derived instances).

msgraph-sdk-dotnet/src/Microsoft.Graph/Generated/Models/BaseDeltaFunctionResponse.cs

Line 13 in b95df6a

public partial class BaseDeltaFunctionResponse : IAdditionalDataHolder, IBackedModel, IParsable

Ideally, using BaseDeltaFunctionResponse as the type parameter would be incorrect as the collection property of the response will have no type/property information to be deserialized into and would cause problems.

Out of curiosity does this work out for you when you use the DeltaGetResponse as the type parameter instead? Is there a specific reason to use the base class here?

[tbithell]

I'll give that a shot. The reason we use the base is we are using the same method to create a PageIterator for both a DeltaGetResponse and a DeltaWithTokenGetResponse.