Add nearvector and neartext to hybrid search

[donomii]

What's being changed:

This patch adds subsearches to hybrid search.

The basic hybrid search runs subsearches with default options. Rather than adding new and complicated ways to customise these subsearches, this patch allows users to directly specify the subsearches, using the same options as the existing nearvector and neartext searches.

To do this, I introduce two new options to hybrid search, NearText: {} and NearVector: {} . These subsearches use exactly the same options and perform exactly the same search as the currently existing searches. The results are then used as usual in hybrid.

In order to do this, I separate the code to generate a http response from the search functions. The search functions can now be used by other code, and have the return type []search.Result. There is now a function called searchResultsToGetResponse, which prepares the http results.

Clients will have to be adjusted to provide access to these subsearches. It would be good if we can share the existing code, so that adding a new feature will appear in hybrid and regular search.

The current, existing hybrid queries continue unchanged

Review checklist

• Documentation has been updated, if necessary. Link to changed documentation:
• Chaos pipeline run or not necessary. Link to pipeline:
• All new code is covered by tests where it is reasonable.
• Performance tests have been run or not necessary.

[sonarcloud]

Quality Gate failed

Failed conditions
11.0% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[dirkkul]

In general I am happy to merge it, but I think it needs a few more tests:

• invalid combinations, making sure that errors are returned correctly
• combinations of query with searches

[Techie5879]

This seems to have been merged. @donomii Has the documentation been updated/how can I use it?

[graphinglife]

e been merged. @donomii Has the documentation been updated/how can I us

Is there documentation we can see?