New endpoint for instant search

added typeRefactoring + 1 deleted label

Ah alex, have you seen my improvements for the MessageComposer search? See the other endpoint in SearchRestController, listUserResultsAction. I don't have statistics for the topbar search but I guess performance there should be quite bad as well. I suggest incorporating (might mean to refactor it a bit) that method at least for user search.

E.g. the logic can be split out to a common "service" and be reused for different searches - this aligns output formatting, shown information and search results between the different options to search a thing. The remaining searches are adding people to store teams and adding people to groups.

Just to make sure, do you mean this should

use the optimised searchUserInGroups for the user search
and add search by id like in listUserResultsAction ?

The output format is a bit different because listUserResultsAction only returns id and a value and the topbar also needs the teaser and possibly a photo url in the future.

I could also split this into multiple endpoints /search/region, /search/stores, and the existing /search/user, but that would add even more load on the database.

I really only meant trying to use the searchUserInGroups gateway method, but it is fine for me to do that later as a second step... I was only thinking about that because currently, data search is really slow without proper fulltext indexes. E.g. I am also thinking about extending search.

I wonder if it wouldn't be great to have a "general search" in the top - I like those. Theoretically, we have really no problem in also search forums etc.. Just the UI needs to be good, and if I enter hello into the topbar, I am maybe a bit confused when I get forum messages.

So maybe we take yours as it is and refactor parts later?