Advanced Unified Search using Search Options

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
It is a missing feature: advanced search in UnifiedSearch.

Describe the solution you'd like
The first implementation would be to allow options within the text field, in the format option:value.
The solution would be to extract those options from the term so the option won't be considered like a keyword by the apps answering to the search request:

As an example, the query-stringkeyword1 option1:value1 keyword2 will be transformed to keyword1 keyword2 while the option1:value1 will feed a SearchOptions model

Current PR is just a quick (and working) workflow. I would love some feedback on that solution from @nickvergessen and @ChristophWurst

Review the current PR linked in the issue and trace UnifiedSearch's handling of the term alongside the SearchOptions model. Done means option:value expressions are separated from the keyword term and supplied as search options without being treated as keywords by responding apps.