v6: Generative queries + Dynamic RAG

[bevzzz]

Here's an example showcasing the new functionality.

client.collections.create(
  "Songs", c -> c
    .generativeModule(Generative.anthropic(a -> a
      .mode("claude-sonnet")
      .maxTokens(2048)
      .temperature(.3f)
      .stopSequences("\n\n", "{end}")
);

var songs = client.collections.use("Songs");

var dissTracks = songs.generate.nearVector(
    myFavouriteSong,
    nv -> nv.distance(0.42f).limit(25),
    generate -> generate.singlePrompt(
      "write a rap diss based on the lyrics",
      rag -> rag.dynamicProvider(DynamicProvider.xai(
        x -> x.model("grok-1").topP(.71f)
      ))
    ),
    GroupBy.property("artist", 5, 5)
);

for (var group : dissTracks.groups().values()) {
   var diss = group.generated().text();
   System.out.printf("Diss track for group %s: %s\n", group.name(), diss);
}

This PR provides support for all generative modules we currently have in Weaviate:

• Anyscale
• Anthropic
• Aws
• Cohere
• Databricks
• Friendliai
• Google
• Mistral
• Nvidia
• Ollama
• OpenAI / Azure
• Xai

DummyGenerative, while defined, is not "advertised" via the static factories in Generative and DynamicProvider classes.

[orca-security-eu]

Orca Security Scan Summary

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

[dirkkul]

DId you think about using separate factories for sagemaker and bedrock?

[bevzzz]

I did but after looking through the docs ("Ask AI") I figured it was only 1 argument each that is special to the service (sagemaker -> endpoint, bedrock -> model).

Providing separate builders for each is not too much work, but I'm leaning towards documenting that in the Javadoc. Wdyt?

[dirkkul]

If it is not much work, I'd prefer the separate builders

But no strong opinion

[bevzzz]

I made this change in a follow-up PR, to avoid tricky rebases and such.

If everything else is fine, I'll proceed with merging this.