Examine powered entity search for documents, media and members

[kjac]

Prerequisites

• I have added steps to test this contribution in the description below

Description

This is the follow-up for #15951 - this time with Examine powering the entity search for documents, media and members. At the same time, this PR ensures that the entity search respects any user start node limitations for the current user.

Testing this PR

The results from the search endpoints in V14 should match the results in V13. In other words, upgrade a database from V13 to V14 and compare the search results.

Also test that user start nodes are being respected. Thus the searches should yield no document or media results "outside" of the current user start nodes.

Don't forget to rebuild the Examine indexes in both versions before comparing 😅

[bergmania]

LGTM tests out good 💪

[bergmania]

Testing the user start nodes are a bit cumbersome, as this is not exposed anywhere. Is this a missing feature somewhere?

In V13, it seems like we use examine search with ignored user start nodes, when searching with a datatype key and that datatype is configured to ignore them

[kjac]

Hep. I believe bypassing the user start nodes is only relevant for documet and media trees at this point.

We can amend the search endpoints later on if necessary, but for the time being they've been explicitly coded to respect user start nodes.

[bielu]

Just noticed this pr, I have aquestion:
Is it a goal to adding more examine tied abstraction, instead of hiding examine implementation?
IExamineEntitySearch imho should be just an implementation for IEntitySearch, so it can be easily swapped for any search provider.... 🤔

[kjac]

Hi @bielu,

It's not a goal 😄 we're certainly still looking towards creating abstraction layers around search to make search providers easier to swap. To that end, IExamineEntitySearch is a bad name I agree. I'll see if I can come up with a better one.

Thanks for chipping in 👍