v6: Re-unite Read-/WriteWeaviateObject

[bevzzz]

This PR replaces Read-/WriteWeaviateObject with a unified WeaviateObject type, effectively reversing #503.

After some discussion it is clear that reference properties are the key difference between the read- / write- objects and that the user needn't be aware of that unless they're working with reference properties.

Inserting data

c.data.insert(WeaviateObject.of(properties, obj -> obj.vectors(Vectors.of(...))));

Metadata fields are now split into those always present (uuid, vectors, timestamps, tenants) and those related to queries (see QueryMetadata).

Querying data

List<WeaviateObject<?>> objects = c.query.nearVector(new float[]{1, 2, 3}).objects();

var first = objects.get(0);
first.uuid();
first.vectors();
first.createdAt();

// Query metadata
first.queryMetadata().distance();

Traversing references

A helper .asWeaviateObject() allows users to cast references into WeaviateObjects for an easier traversal

var searchResult = c.query.fetchObjects(q -> q.returnReferences(
  QueryReference.single("friendsWith", ref -> ref.returnProperties("birthday"))
));

searchResult.objects().forEach(object -> {
  object.references().forEach((propertyName, ref) -> {
    // Values that are always available
    ref.uuid();
    ref.collection();
    
    // Getting properties of the reference object requires type-casting
    ref.asWeaviateObject().properties().get("birthday");
  });
});

[orca-security-eu]

Orca Security Scan Summary

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