Fix incorrect URLs for next/previous URLs

[AbegaM]

Purpose of PR

• This pull request addresses an issue with the /tables/invoices/rows API endpoint. When a request is sent to this endpoint, the response includes the data in the invoices column, as well as next and prev keys that allow the user to navigate between pages of results. However, as seen in the example response below, the URL parameters in the next field are incorrect. Specifically, the page parameter should be updated to _page, and if a user passes other parameters such as _ordering, _filters, _limit, _schema, _extend, and _search, these parameters are not displayed in the next and prev fields.

Example response:

  {
    "data": [
        {
            "InvoiceId": 1,
            "CustomerId": 2,
            "InvoiceDate": "2009-01-01 00:00:00",
            "BillingAddress": "Theodor-Heuss-Straße 34",
            "BillingCity": "Stuttgart",
            "BillingState": null,
            "BillingCountry": "Germany",
            "BillingPostalCode": "70174",
            "Total": 1.98
        }
    ],
    "total": 412,
    "next": "/tables/invoices?page=2",
    "previous": null
}

Modification

• To address this issue, I have modified the code in the core/src/controllers/rows.js file. Specifically, I have ensured that all query parameters that are added by the user are included in the next and prev fields of the API response. This ensures that users can properly navigate between pages of results, even when additional query parameters are present.

• To test this PR you can use the URL below

  localhost:8000/api/tables/invoices/rows?_filters=BillingCountry:Brazil&_search=SP&_ordering=-Total&_schema=customerId&_extend=CustomerId

[AbegaM]

@thevahidal and @IanMayo Please review this PR, i have fixed the errors in the next/prev fields

[AbegaM]

@IanMayo can you please retest it now?