$skipToken is replaced with $skip when $compute is used

Assemblies affected
ASP.NET Core OData 8.x

Describe the bug
NextLink does not have $skipToken even when configured, but instead has $skip when a $compute expression is used in the request.

Reproduce steps

1. Enable SkipToken for your controllers.
2. Hit your API service with a $compute expression:

http://localhost:2000/beta/students?$orderby=lowername&$compute=tolower(name) as lowername

Data Model

public class Student
{
    [Key]
    public string Id {get; set;}
    public string Name {get; set;}
}

EDM (CSDL) Model

<EntityType Name="Student">
    <Key>
        <PropertyRef Name="id" />
    </Key>
    <Property Name="id" Type="Edm.String" Nullable="false" />
    <Property Name="name" Type="Edm.String" Nullable="false" />
</EntityType>

Request/Response

http://localhost:2000/beta/students?$orderby=lowername&$compute=tolower(name) as lowername

Expected behavior
NextLink in the response should have a $skipToken, but it instead has a $skip.

Screenshots
NA

Additional context

1. The default SkipToken handler is used.
2. The same code returns a $skipToken when used without the $compute expression and even with just the $orderby expression.

Reproduce the request using the default SkipToken handler with $orderby and $compute, then compare the generated NextLink with the behavior without $compute. Trace the pagination and NextLink generation path; done means the response retains $skipToken when $compute is present, without regressing the existing cases.