v6: Throw WeaviateApiException for error status codes

[bevzzz]

Closes #403

This PR adds explicit error handling logic to the HTTP and gRPC transport. Previously both would either "swallow" a bad status code entirely or leak the internals by throwing something like io.grpc.StatusRuntimeException, which made error handling difficult or, at times, impossible.

While error handling is transparent in the sense that both gRPC and HTTP transports throw the same WeaviateApiException, users may still encounter an IOException thrown by the HTTP transport. At the moment we do not catch/wrap it, because those errors would not be Weaviate-specific (e.g. timeout, connection reset by peer, etc) and are better handled separately.

💡 WeaviateException is the base class for handling any Weaviate-related exceptions. It's useful when we only want to log/propagate the exception.

HTTP requests

var things = client.collections.use("Things");

try {
  things.data.insert(Map.of("title", "Red balloon"), thing -> thing.uuid("invalid"));
} catch (WeaviateApiException e) {
  System.out.println(e.getMessage());
  // Outputs: HTTP 422, POST /v1/objects: id "invalid" is not a valid UUID
}

gRPC Requests

var things = client.collections.use("Things");

try {
  things.query.bm25("red balloon", q -> q.returnProperties("unknown"));
} catch (WeaviateApiException e) {
  System.out.println(e.getMessage());
  // Outputs: UNKNOWN: class Things does not have property "unknown"
}

Pagination

WeaviatePaginationException preserves information about the pageSize and the last cursor used. The original exception is accessible via e.getCause() (can be WeaviateApiException or some other IOException).

var unknown = client.collections.use("Unknown");

String lastCursor;
try {
  unknown.paginate().forEach(System.out::println);
} catch (WeaviatePaginationException e) {
    lastCursor = e.cursor();
}

Endpoint utility classes

Inspired by Elasticsearch's Endpoint pattern, the new SimpleEndpoint, OptionalEndpoint, and BinaryEndpoint reduce boilerplate in how HTTP requests are defined.

Removed deprecated vectorizeClassName parameter

Using this parameter is highly discouraged. We remove it from all vectorizers but one, text2vec-contextionary, because Weaviate will default to true, which does not allow creating collections with underscores in their names. That's annoying, so we make it read-only in the public API and always send false in the request.

[orca-security-eu]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Secrets	0   0   0   0	View in Orca