Improve inconsistent Pagination and Asset Ordering in API Responses

The same paginated API call is returning inconsistent asset ordering and missing records across identical requests. Pagination becomes unreliable, which breaks automation and integration processes that depend on consistent asset retrieval.

E.g.

1. layoutid=16&companyid=1&page=1&per_page=100

2. layoutid=16&companyid=1&page=2&per_page=100

In these two examples the asset order would change between responses with no stable sort.