fix: pagination results between azure and gcp providers
This MR provides a consistent way to handle pagination between GCP and Azure implementations
During pagination, when NO_MORE_RESULTS
can be obtained, both in GCP and Azure implementations, nextPageCursor
will always be set to "" (empty string)
Edited by Varunkumar Manohar