[BUG] AAS Environment - paging

[chbo-ml]

Describe the bug
a cursor is returned, even when returned the last element in /shells endpoint.

To Reproduce
Steps to reproduce the behavior:

I have 2 AssetAdministration Shells in my Repository (docker container aas environment).
When invoking the GET /shells endpoint with a limit of 1 without a cursor, I get correct result with paging_metdatata and with a cursor.
When i Ivoke the /shells endpoint with this cursor and limit 1 I get correct, the next asset administration shell, but addionally a paging_metdata result with a cursor. Because the second aas returned was the last in the repository there should be no cursor.
When i again call /shells ith the given cursor corretly no result is returned.

Expected behavior
IDTA spec tells:
"The cursor for the next part of the result set. No cursor attribute means that the end of the result set has been reached. "
So I would expect no curesor when invoking the /shells endpoint with the cursor returned by the first call.

BaSyx (please complete the following information):
image: eclipsebasyx/aas-environment:2.0.0-SNAPSHOT

[aaronzi]

Hi @chbo-ml,

thank you for the bug report. We will have a look at this.