[full-ci] enhancement: add support for natural language kql date ranges

[fschade]

Description

follow up pr for the ocis kql integration, as the spec describes kql is able to select date ranges by writing natural language.

The following ranges are described in the spec and therefor supported by the ocis implementation:

• Mtime:today - range: start of today till end of today
• Mtime:yesterday - range: start of yesterday till end of yesterday
• Mtime:"this week" - range: start of this week till end of this week
• Mtime:"this month" - range: start of this month till end of this month
• Mtime:"last month" - range: start of last month till end of last month
• Mtime:"this year" - range: start of this year till end of this year
• Mtime:"last year" - range: start of last year till end of last year

the ast will extended as follow:

	&ast.Ast{
		Nodes: []ast.Node{
			&ast.DateTimeNode{
				Key:      "Mtime",
				Operator: &ast.OperatorNode{Value: ">="},
				Value:    mustParseTime(t, "2023-09-10"),
			},
			&ast.OperatorNode{Value: kql.BoolAND},
			&ast.DateTimeNode{
				Key:      "Mtime",
				Operator: &ast.OperatorNode{Value: "<="},
				Value:    mustParseTime(t, "2023-09-10 23:59:59.999999999"),
			},
		},
	},

	&ast.Ast{
		Nodes: []ast.Node{
			&ast.DateTimeNode{
				Key:      "Mtime",
				Operator: &ast.OperatorNode{Value: ">="},
				Value:    mustParseTime(t, "2023-09-09"),
			},
			&ast.OperatorNode{Value: kql.BoolAND},
			&ast.DateTimeNode{
				Key:      "Mtime",
				Operator: &ast.OperatorNode{Value: "<="},
				Value:    mustParseTime(t, "2023-09-09 23:59:59.999999999"),
			},
		},
	},

and so on....

following queries are now exactly covered as described in the spec:

* 2.1.2 AND Operator 
* 2.1.6 NOT Operator
* 2.1.8 OR Operator
* 2.1.12 Parentheses
* 2.3.5 Date Tokens
* 3.1.11 Implicit Operator
* 3.1.12 Parentheses
* 3.1.2 AND Operator
* 3.1.6 NOT Operator
* 3.1.8 OR Operator
* 3.2.3 Implicit Operator for Property Restriction
* 3.3.1.1.1 Implicit AND Operator
* 3.3.5 Date Tokens

beside that it also includes:

• structured table tests

Related Issue

• [full-ci] - use KQL as default search query language #7212
• enhancement: Keyword Query Language (KQL) search syntax support #7043
• fix unary in the beginning. add tests #7247
• [test-only] KQL api search tests #7248
• [full-ci] enhancement: add more kql spec tests and simplify ast normalization #7254
• [full-ci] enhancement: add more kql spec tests and simplify ast normalization #7254
• [full-ci] - use KQL as default search query language web#9653
• [tests-only] replaced the search test web#9672
• [ocis] Use KQL for existing search syntax #7042
• [ocis]enable KQL in ocis #7179
• [search] No response from server while searching inside a folder containing space in name #7114
• [web] change bleve query language to KQL web#9636
• Search: scope select has wrong initial state web#9646

Motivation and Context

implement the spec

How Has This Been Tested?

• unit tests
• acceptance tests
• e2e tests

Screenshots (if appropriate):

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 only (no source changes)

Checklist:

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

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
7 Code Smells

88.7% Coverage
0.0% Duplication