[FEATURE REQUEST] Pagination for list of assets in AvailableAssets

[jckastel]

Is your feature request related to a problem? Please describe.

The /operator/available-assets API response currently contains an optional assets field which contains a list of individual Assets. However, this list could grow quite large and there is currently no way to limit the number of entries in this list. The list is required by certain third parties that make use of TOMP, such as CROW. There are pagination settings for the query as a whole starting from v1.1.0, but these presumably apply to the list of asset types, not to the nested list of individual assets per type.

Urgency

Major; at least one party already makes use of this functionality and it could lead to performance issues for parties with large numbers of assets. See also issue #425 for additional reasons why pagination should be required.

Describe the solution you'd like

Aside from the existing pagination options for AssetTypes, we would like to add pagination support to the lists of assets.

Possible Implementation

Note that, since there are multiple lists of assets (i.e. one per type), to do this properly and in a way that is clear to developers, it may be desirable to split the existing AvailableAssets endpoint into two parts; one for requesting the list of asset types (without the assets field that currently exists in 1.3.0), and one endpoint to request assets of a specific type in a follow-up request, with both endpoints supporting pagination.

[edwinvandenbelt]

Use HAL in v2.0