Fix parsing of floats in $apply/aggregate/average expression

[gathogojr]

Issues

This pull request fixes issue #1809.

Description

Fixes a bug where ApplyBinder does not cater for float/single for the average aggregate method. This causes the following average expression to be rejected:

$apply=aggregate(SingleProp with average as AverageSingleProp)

while related sum, min, and max are accepted

$apply=aggregate(SingleProp with sum as SumSingleProp)
$apply=aggregate(SingleProp with min as MinSingleProp)
$apply=aggregate(SingleProp with min as MaxSingleProp)

Note: The return value from averaging floats should be a float
https://docs.microsoft.com/en-us/dotnet/api/system.linq.enumerable.average?view=netcore-3.1#System_Linq_Enumerable_Average__1_System_Collections_Generic_IEnumerable___0__System_Func___0_System_Single__
https://docs.microsoft.com/en-us/dotnet/api/system.linq.enumerable.average?view=netcore-3.1#System_Linq_Enumerable_Average__1_System_Collections_Generic_IEnumerable___0__System_Func___0_System_Nullable_System_Single___

Checklist (Uncheck if it is not completed)

• Test cases added
• Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

[KenitoInc]

LGTM

[KenitoInc]

Even though a float is EdmPrimitiveTypeKind.Single, Maybe for a better description, you could have used FakeSingleFloatPrimitive

[gathogojr]

I could do that

[xuzhg]

[kosinsky]

🚀