[full-ci] - use KQL as default search query language

[fschade]

Description

We've introduced KQL as our default query language.
Previously we used our own simple language for queries which is now replaced by kql.

sample.tx* Tags:important Tags:report Content:annual*

becomes

name:"sample.tx*" AND tag:important AND tag:report AND content:"annual*"

by default KQL uses AND as property restriction and the query described above can also be formulated as follows

name:"sample.tx*" tag:important tag:report content:"annual*"

More advanced syntax like grouping combined with boolean property restriction is supported too

(name:"sample*" name:"*txt") tag:important OR tag:report content:"annual*"

Related Issue

• [full-ci] - use KQL as default search query language ocis#7212
• [ocis] Use KQL for existing search syntax ocis#7042
• [ocis]enable KQL in ocis ocis#7179
• [search] No response from server while searching inside a folder containing space in name ocis#7114
• enhancement: Keyword Query Language (KQL) search syntax support ocis#7043
• [web] change bleve query language to KQL #9636
• Search: scope select has wrong initial state #9646

Motivation and Context

Defining a own query language is error prone and leads to a lot of documentation, the oCIS team decided in that ADR to use KQL as our standard. A clear set of rules is set by MS and the dictionary fits well in our usecase.

How Has This Been Tested?

• unit tests have been adjusted
• acceptance tests have been adjusted

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

95.7% Coverage
0.0% Duplication