Limit lists size in internal apis and on server rendered pages

[alexdln]

We currently have no restrictions on queries or their length for a number of locations. This primarily applies to search and organizations (including YOLO option).

All requests we run and process on our server must be limited. This is important for the performance of all users and costs.
This concerns both the processing of the requests themselves (downloading and passing all records through parsers) as well as the rendering process itself (rendering 10,000 elements on the server is an expensive operation in terms of performance).

We shouldn't sacrifice 50ms of experience of ten other users for the sake of one user who likes to receive large lists. This also applies to an overly opened API, in which we have an easy point for a DDoS attack on us

Usually the limit is set to 100 records, but for our search we need to set limit to 500 items for search.

[parion]

I'll begin looking into adding pagination to the api/registry/org/{(org)}/packages endpoint. If successful, I'll look at adding those to other list-related responses.

If there's some alternative means to hook into Nuxt routing to throttle all list-related response, please let me know.