feat: Add Boost API

[trengrj]

Adds Boost features weaviate/weaviate#11103 to python client.

Near Vector/Object/XYZ operators now support a boost parameter.

Boost.property - for property boosts
Boost.filter - for filter boosts
Boost.numeric_decay for numeric decay boosts
Boost.time_decay for time decay boosts
Boost.blend for combining multiple boosts together.

All allow for an optional depth and weight parameter to control boosting impact. Time decay has a _decay_value_to_str helper for supporting python time values.

Property modifiers and Decay curves have constants.

Integration test added with 1.38 gate.

[orca-security-eu]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[codecov-commenter]

Codecov Report

❌ Patch coverage is 67.28395% with 53 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (dev/1.38@c307d97). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
integration/test_collection_boost.py	63.63%	20 Missing ⚠️
weaviate/collections/grpc/query.py	29.16%	17 Missing ⚠️
weaviate/collections/classes/grpc.py	80.72%	16 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             dev/1.38    #2030   +/-   ##
===========================================
  Coverage            ?   86.57%           
===========================================
  Files               ?      300           
  Lines               ?    23051           
  Branches            ?        0           
===========================================
  Hits                ?    19957           
  Misses              ?     3094           
  Partials            ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bevzzz]

Suggested change

	def property( # noqa: A003
	def numeric_property( # noqa: A003

suggestion: if numeric_decay has the "numeric_" prefix to highlight that it's only applicable to numeric properties, then I'd argue this method should have it as well

[trengrj]

We won't make a timestamp_property operator as Timestamps need a sensible scale. I'm open to changing it to numeric_property but it feels a bit more confusing to users.

[bevzzz]

numeric_property but it feels a bit more confusing to users

My speculation is that property suggest any property (bool, text, blob) can be used, whereas numeric_property sort of constraints that ==> less confusing.

Ofc that is unless we are planning to extend Boost in a way that, say, a text property can be boosted too, and that'll use Boost.property.

[trengrj]

Maybe it makes more sense like this:

1. Boost.property is for values that have meaningful ranking value and is intended as the simplest operator (boost by popularity). Currently this supports numeric but ideally later on I'd like to support bool as well.
2. Boost.filter is for categorical or text values. You provide a standard filter object.
3. Boost.time_decay and Boost.numeric_decay are more advanced operators. They are separated by type because the paramters (origin = now vs origin = 0) and scale ("7d" vs 7) are different enough that we have separate gRPC messages and parsing logic.

So in this case there won't ever be a Boost.text_property you would just use Boost.filter instead.

[bevzzz]

Agreed 👌

but ideally later on I'd like to support bool as well

Out of curiosity: is my understanding correct that boosting a bool property should have the same mechanics under the hood as boosting a "categorical" (Boost.filter) property? Given you can turn filter results into boolean [true, false, true, true].

[orca-security-eu]

Orca Security Scan Summary

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