Remove old page-based pagination from /ras/runs API in favour of cursor-based pagination

[eamansour]

Story

As a Galasa maintainer, I want to remove the existing slow page-based pagination from the /ras/runs API and replace it with the new cursor-based pagination, so that REST API users benefit from the increased performance of cursor-based pagination.

Background

This story assumes 0.37.0 has been released and the development version is now at 0.38.0.

As part of #1921, cursor-based pagination was added to the /ras/runs endpoint that could be enabled/disabled using the includeCursor query parameter. This was added because the existing page-based pagination was much slower due to it retrieving all the runs matching a given query and discarding the runs that aren't in the page requested, every time a page was requested.

A PR was opened to replace the old page-based pagination with the new approach galasa-dev/framework#627 - it wasn't merged in to avoid causing issues with backwards compatibility. With the release of 0.37.0, there has been enough time for clients to migrate to using cursor-based pagination, so the old pagination can be removed.

Tasks

• Merge Replace page-based pagination with cursor-based pagination in /ras/runs framework#627 (ensuring the changed bundles are at 0.38.0)
• Remove the includeCursor query parameter from the CLI runs get code