ODSP duplicate delta function

ODSP defines two OData functions when only one is required

<Function Name="delta" IsBound="true">
   <Parameter Name="bindingParameter" Type="graph.driveItem" />
   <ReturnType Type="Collection(graph.driveItem)" />
</Function>
<Function Name="delta" IsBound="true">
  <Parameter Name="bindingParameter" Type="graph.driveItem" />
  <Parameter Name="token" Type="Edm.String" Unicode="false" />
  <ReturnType Type="Collection(graph.driveItem)" />
</Function>

During the conversion, this leads us to project the following paths

• {+baseurl}/drives/{drive%2Did}/items/{driveItem%2Did}/delta{?%24top,%24skip,%24search,%24filter,%24count,%24select,%24orderby}
• {+baseurl}/drives/{drive%2Did}/items/{driveItem%2Did}/delta(token='{token}'){?%24top,%24skip,%24search,%24filter,%24count,%24select,%24orderby}

Which creates confusion for consumers, they start parsing delta links when they shouldn't. etc...
The only scenario where we need to support a token (not deltaToken) query parameter is when users only want to start from the latest with ?token=latest

We should implement a transformation to

1. remove the second function
2. add the token query parameter to the first function