Add documentation for terms_set minimum_should_match parameter

[mspielberg]

Elasticsearch has supported the minimum_should_match parameter for the terms_set query since 8.10.0 (PR #96082). As mentioned in the original issue ticket (#94095) the additional parameter is not currently documented, so this PR adds documentation.

This PR also removes the incorrect documented constraint that the terms parameter must consist solely of strings. In fact each term can be any valid FieldValue, as in the normal terms query.

For example, when querying against a field mapped as type date the term may be specified with a JSON number as described at (https://www.elastic.co/guide/en/elasticsearch/reference/8.15/date.html).

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[elasticsearchmachine]

Pinging @elastic/es-search (Team:Search)

[leemthompo]

@elasticmachine test this

[leemthompo]

run docs-build

[leemthompo]

@pquentin approved the corresponding spec changes, does this look good to you? :)

[pquentin]

Thanks! This looks good to me, I just added two nits about the documented types.

Sorry for the reviewing delay.

[pquentin]

Why remove "array of strings" here?

[mspielberg]

See the PR description. The elements are not restricted to string, but can be anything parsable to a field value, including JSON “number” types. Documenting as “array of strings” is incorrect and misleading.

[pquentin]

Suggested change

	(Optional) Specification for the number of matching terms required to return
	a document.
	(Optional, integer) Specification for the number of matching terms required to return
	a document.

[mspielberg]

Restricting to “integer” is incorrect. The value can be anything described on the linked documentation page, some of which are integers, but also many of which are strings with very specific formats:

https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-minimum-should-match.html