Enforcement of pagination on API endpoints and change of maxPagesize - September release (8.25)

[#1]

Couple of things:

1. maxPagesize has been increased from 100 to 500 on all endpoints. Swagger documentation will be updated in the next release to reflect this.
2. We will introduce pagination on purchaseReceipt and purchaseReceiptBasic endpoint for 8.25. Enforcement of pagination will be in future versions.
3. Following endpoints will have enforced paging for 8.25:

   /api/v1/cashsale
   /api/v1/country
   /api/v1/customerCreditNote
   /api/v1/customerCreditWriteOff
   /api/v1/customerDebitNote
   /api/v1/customerOverdueCharge
   /api/v1/customerSalesPrice
   /api/v1/deferralCode
   /api/v1/employee
   /api/v1/GeneralLedgerTransactions
   /api/v1/inventoryadjustment
   /api/v1/inventoryissue
   /api/v1/inventoryReceipt
   /api/v1/inventoryTransfer
   /api/v1/location
   /api/v1/payment
   /api/v1/projectbasic
   /api/v1/purchaseorderbasic
   /api/v1/salesordertype
   /api/v1/supplierPayment
   /api/v1/vatZone

4. To align maxPagesize for all endpoints, the payment endpoints (customerPayment, supplierPayment and Payment) will have their maxPagesize decreased from 5000 to 500 for 8.25

We would also like to stress that the maxPagesize variable must not be hard coded as it can be changed without notification, based on our monitoring.