[ML] Do not match time series counter fields with aggs in wizards

[jgowdyelastic]

Time series counter metric fields are treated as non aggregatable and are not matched with aggregations in the new_job_caps endpoint.
This removes them from the detector dropdowns in all wizards where we match functions(aggs) to fields.
e.g.

Note, the fields are not entirely removed from the new_job_caps response. So they are still available in other dropdowns.

This fixes an issue where having counter fields available for selection would cause an error.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[droberts195]

It might be possible to do something better than this for 8.8. elastic/elasticsearch#93884 is adding a list of supported aggregations. There's a CCS complication but a suggestion of how to deal with that in elastic/elasticsearch#93884 (comment).

Depending on the resolution of the CCS issue we should do one of the following:

• Merge this PR for 8.8, then do something better in 8.9 by making use of the list of available aggregations per field
• Make use of the list of available aggregations per field in 8.8, assuming something sensible is being returned in the case of CCS against 8.7 clusters

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 33dbfeb

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
ml	3.4MB	3.4MB	+32.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	433	436	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	513	516	+3

History

• 💚 Build #113246 succeeded d28c820
• 💔 Build #113035 failed 77b380f

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @jgowdyelastic

[peteharverson]

Tested and LGTM.

As @droberts195 suggested, once elastic/elasticsearch#93884 is in, we should look to show these field types and check the available aggregations.