It has unique way to handle paging, first the json structure is not as recommended by the standard http pagination also there is something called $skipToken that also need to be passed in the next call.
I have built wrapper logic app that will action as proxy and convert the ResourceGraph response to paging enabled response
In your business logic app instead of calling the ResourceGraph Endpoint you will call the wrapper logic app
By adopting the wrapper concept, you will avoid implementing the until loop pattern since you will utilize the built-in pagination inside the Http action
How the wrapper is working
Initialize the next Link variable by getting the value from triggerOutputs()['queries']?['nextLink']