…arch

+ Extended Serializer.array to support nested arrays.

Updated integration test to use multiple target feature.

Previously BaseClient would "swallow" these errors,
assuming HTTP 200 means a successful request.
However, GraphQL specs allow it to send status 200
alongside a response body with a list of errors.

In v1.27 sending a replication request which requests more
nodes than is available produces a different error message.

It seems that in v1.27 the "groupBy" property should be requested as well,
otherwise the server returns fewer results than before.

This commit mirrors changes in the Go client:
weaviate/weaviate-go-client@6fa31b9

WeaviateClass has a default filter strategy "sweeping"

In contrast to the previous implementation, this approach
inverts the dependencies: BaseClient provides a mechanism
for an external class to extract errors from "custom" locations
in the response body, while staying entirely unaware of the
concrete classes that might do that.

Fix invalid @returns tag in Javadoc

BaseClient will give GraphQLResponse special treatment

- Renamed FilterStrategy enum
- Dropped default values for filtera and deletion strategy configs