Getting status of instances does not support continuation token

It seems that as much as C# version of the library supports continuation token while iterating over execution instances with History API, NodeJS does not. Instead, it tries to encapsulate iteration process by managing continuation token itself.
Unfortunately, as much as some people may consider it useful, in general, it is quite limiting. It is limiting for wrong reasons - it would be nice to keep the API on par with C# one as much as possible for consistency.

Imagine you have 100K executions. Do you really want to fill up your process' memory with 100K rows or let the user decide how the paging over will be implemented e.g. read 1000 rows, process them, dispose, then another 1000 rows, etc. ?

Start by inspecting the NodeJS History API used to iterate over execution instances and compare its continuation-token behavior with the C# library. Confirm how paging currently manages the token, then define an API that lets callers process pages without accumulating all executions in memory; done means continuation-token paging is supported consistently.

Written by the indexing model from the issue text.