Add support for new `generative-digitalocean` module

[antas-marcin]

This is a new module that will come out with latest v1.37+ Weaviate versions:

Here are the links to proto messages:

GenerativeDigitalOcean
GenerativeDigitalOceanMetadata

Available settings are:
baseURL - string (defaults to: https://inference.do-ai.run)
model - string (defaults to: llama-4-maverick)
temperature - *float64
topP - *float64
maxTokens - *int
frequencyPenalty - *float64
presencePenalty - *float64
stop - []string

[denis-samatov]

Hi @antas-marcin — I'd like to take this on. I checked python-client main at 0791933 and the current server generative.proto. The implementation appears to require: (1) GenerativeSearches.DIGITALOCEAN plus Configure.Generative.digitalocean(...) for collection configuration, (2) a runtime _GenerativeDigitalOcean / GenerativeConfig.digitalocean(...) mapping to GenerativeProvider.digitalocean, including stop as TextArray, (3) refreshed protobuf bindings for the supported protobuf runtimes, and (4) focused coverage in test_config.py and test_classes_generative.py plus the changelog. I also confirmed there is currently no open DigitalOcean PR. One question before I start: server main now also contains GenerativeMeta, added after this issue. Would you prefer the protobuf refresh to include both new wire types while keeping the public Python API changes in this PR DigitalOcean-only, or should I pin generation to the DigitalOcean proto commit so the generated diff stays isolated?

[g-despot]

Hi @denis-samatov, thanks for volunteering 😄

Just one warning, this task is time critical, we would like to have it shipped before the end of this week. If you do decide to take this on, please check "Allow edits from maintainers" when creating the PR so I can make edits directly and get it over the finish line fast. And if the timeline doesn't work for you, just say so and I'll cover it, you can also take on another issue that suits you.

On the proto question: regenerate from the tip of main (weaviate/proto/v1/regen.sh) and let the generated files include both GenerativeDigitalOcean and GenerativeMeta. Keep the public Python API changes DigitalOcean-only.

[g-despot]

Hi @denis-samatov! Thanks again for the contribution. You need to post a comment in your PR agreeing to the CLA.