"Smart"/dynamic default page size-ing?

[yarikoptic]

Make paging smarter. Might be a little non-trivial to implement on django side (although didn't research -- might have been already done etc), but I think we might benefit from having first pages to be small (e.g. default 100) but then if request is going through subsequent pages -- make them as large as we can afford (or just 1000).
This way overall we can decrease desired number of requests for e.g. listing /assets in a dandiset 10-fold while consuming the same bandwidth (well -- actually even save that a little but not significantly).

For client code I believe it should not matter how many are actually returned in the response if no explicit page_size was requested.

ref:

• Slow response times from asset list endpoint #1891