Lock page token to a given tree in GetTreeEntries
GetTreeEntries
support paging the tree entries it returns as the list can be long. The page token returned does not include the tree oid and can thus page across two different trees leading to incorrect results. We should include the tree oid in the page token and use it to ensure the page token is always used to access a given tree only. More details at: !4870 (comment 1122139728)