IBX-6827: Aggregation API improvements

[adamwojs]

Question	Answer
JIRA issue	IBX-6827
Required by	ibexa/solr#56, ibexa/elasticsearch#31
Type	feature
Target Ibexa version	v4.6
BC breaks	no

This PR introduces several small Aggregation API improvements (DX).

Range::INF

Ibexa\Contracts\Core\Repository\Values\Content\Query\Aggregation\Range::INF const allows developers to be more verbose when defining open ranges:

// Before:
new Range(null, 100)

// After:
new Range(Range::INF, 100)

Range labels

Added label property with accessors to \Ibexa\Contracts\Core\Repository\Values\Content\Query\Aggregation\Range class.

new Range(Range::INF, new DateTime("01-01-2023"), "Published before 2023")

Labels can used latter on to render aggregation results.

Simplified access to Term & Range Aggregations Result keys

It's very common to use term aggregations to get top N terms e.g 10 most popular categories.

$aggregation = new TaxonomyEntryIdAggregation('most_popular_categories');
$aggregation->setLimit(10);

In this use case we are not interested into how many object belongs to specific bucket. \Ibexa\Contracts\Core\Repository\Values\Content\Search\AggregationResult\TermAggregationResult::getKeys method allows to retrieve terms without need to manually iterate over result entries.

Ranges generators

Step generators

$generator = new DateTimeStepRangesGenerator(new DateTime('2023-01-01'), new DateTime('2023-12-31'));
$generator->setStep(new DateInterval("P1M"));
$generator->setRightOpen(false);
$generator->setLeftOpen(true);

$aggregation = new DateRangeAggregation('enent_by_date', 'event', 'date', $generator->generate());

Related PRs:

• IBX-6827: Aggregation API improvements solr#56
• https://github.com/ibexa/elasticsearch/pull/31

Checklist:

• Provided PR description.
• Tested the solution manually.
• Provided automated test coverage.
• Checked that target branch is set correctly (main for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review (ping @ibexa/engineering).

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
5.6% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
7 Code Smells

No Coverage information
2.6% Duplication