Filtering of elements at backend only

[mdanish98]

The current implementation of CrudRepository does filtering InMemory only. However, it should be done at backend side only based on specific implementation.

Affected methods:
getAll*() -> Pagination

User Story/Explanation

Rules

Refactor our implementation of the crud Repository
in our getAllAas, instead of findAll(), check out Spring crud Repository Method findAllByIds(Iterable id)

Entry Points

aasrepository: https://github.com/eclipse-basyx/basyx-java-server-sdk/blob/main/basyx.aasrepository/basyx.aasrepository-backend/src/main/java/org/eclipse/digitaltwin/basyx/aasrepository/backend/CrudAasRepository.java
submodelrepository: https://github.com/eclipse-basyx/basyx-java-server-sdk/blob/main/basyx.submodelrepository/basyx.submodelrepository-backend/src/main/java/org/eclipse/digitaltwin/basyx/submodelrepository/backend/CrudSubmodelRepository.java
dc repository: https://github.com/eclipse-basyx/basyx-java-server-sdk/blob/main/basyx.conceptdescriptionrepository/basyx.conceptdescriptionrepository-core/src/main/java/org/eclipse/digitaltwin/basyx/conceptdescriptionrepository/ConceptDescriptionRepository.java
discovery: https://github.com/eclipse-basyx/basyx-java-server-sdk/blob/main/basyx.aasdiscoveryservice/basyx.aasdiscoveryservice-backend/src/main/java/org/eclipse/digitaltwin/basyx/aasdiscoveryservice/backend/CrudAasDiscovery.java

Acceptance Criteria

Risks and Assumptions

References & Notes

Dependencies and Blockers