[FEATURE] Default pagination on Registries

[mm-mse]

Is your feature request related to a problem? Please describe.
Currently there is no default pagination in place, when requesting e.g. the aas/ submodel registry.
This is especially problematic when using the current AAS WebUI that doesn't do pagination either and a registry with >100k shells as the requests take long and have a huge response body.
This is also a security issue as an attacker could just omit the limit for pagination for a DoS attack

Describe the solution you'd like
There should be a server side default pagination parameter that is applied if a request does not contain a limit.
It should also be configurable through a config.
The server should enforce a maximum limit for pagination to reduce the attack vector and give more control to the server.
This should be applied to all components like discoveries, registries and environment and relevant endpoints.

Describe alternatives you've considered
No alternative.

Additional context
Tested with ~120k shells on java aas registry hosted in azure container app with /shell-descriptors endpoint: Response time: 25s, response size: 38MB

[aaronzi]

Makes sense to have this default. It's also in the specification (Part 2). I guess there was a reason why we intentionally did not add a default limit but I can't remember it anymore. The only "problem" that I see here is that an implementation for pagination would be needed in the BaSyx AAS Web UI. Otherwise it would be not possible to get to all shells available.

Default limit: 100