Add tracking for query rule types

[kderusso]

This PR adds tracking for query rule types.

The List Query Rulesets PR has been updated to include total rule types. Here is an example updated response:

{
  "count": 2,
  "results": [
    {
      "ruleset_id": "my-ruleset",
      "rule_total_count": 3,
      "rule_criteria_types_counts": {
        "always": 3
      },
      "rule_type_counts": {
        "exclude": 1,
        "pinned": 2
      }
    },
    {
      "ruleset_id": "my-ruleset2",
      "rule_total_count": 3,
      "rule_criteria_types_counts": {
        "always": 3
      },
      "rule_type_counts": {
        "exclude": 1,
        "pinned": 2
      }
    }
  ]
}

The _xpack/usage call also propagates these stats. Here is an example of the updated enterprise_search section:

"enterprise_search": {
    "available": true,
    "enabled": true,
    "search_applications": {
      "count": 0
    },
    "analytics_collections": {
      "count": 0
    },
    "query_rulesets": {
      "total_rule_count": 6,
      "rule_criteria_total_counts": {
        "always": 6
      },
      "total_count": 2,
      "min_rule_count": 3,
      "max_rule_count": 3,
      "rule_type_total_counts": {
        "pinned": 4,
        "exclude": 2
      }
    }
  }

[elasticsearchmachine]

Hi @kderusso, I've created a changelog YAML for you.

[elasticsearchmachine]

Pinging @elastic/search-eng (Team:SearchOrg)

[elasticsearchmachine]

Pinging @elastic/search-relevance (Team:Search - Relevance)

[ioanatia]

is this going to be an issue when we backport to 8.x? not saying we should necessarily change it here, but maybe when we backport we might need to?

[markjhoy]

buildkite test this

[elasticsearchmachine]

💔 Backport failed

Status	Branch	Result
❌	8.16	Commit could not be cherrypicked due to conflicts
❌	8.15	Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 116357

[markjhoy]

@ioanatia and @kderusso - I was able to get this merged - however, backporting this to the 8.16 and 8.15 branches are failing - and trying to run backport --upstream elastic/elasticsearch --pr 116357 is showing a good amount of changes - especially in the TransportVersions.java file - which could be tricky if these changes are pushed there... any ideas / guidance?

[afoucret]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Questions ?

Please refer to the Backport tool documentation