Resume stage workers from where they stopped - Bitbucket Cloud

This is a similar issue with #450831 (closed) but for Bitbucket Cloud. See my comment in here

Bitbucket Cloud's stage workers don't continue from the last processed API page in case of an interruption; instead, they restart from the first API page. Stage workers should store the last processed page in Redis and continue from it in case of an interruption; this way, it guarantees that, eventually, all pages will be processed.

Bitbucket Cloud Documentation: https://developer.atlassian.com/cloud/bitbucket/rest/intro/#pagination

However, clients are not expected to construct URLs themselves by manipulating the page number query parameter. Instead, the response contains a link to the next page. This link should be treated as an opaque location that is not to be constructed by clients or even assumed to be predictable. The only contract around the next link is that it will return the next chunk of results.

It is important to realize that Bitbucket support both list-based pagination and iterator-based pagination. List-based pagination assumes that the collection is a discrete, immutable, consistently ordered, finite array of objects with a fixed size. Clients navigate a list-based collection by requesting offset-based chunks. In Bitbucket Cloud, list-based responses include the optional size, page, and previous element. The the next and previous links typically resemble something like /foo/bar?page=4.