[Mappings Editor] allow time series related properties

[Dosant]

Summary

Fix #139922

This pr adds a definition for time_series properties to the mappings editor.
This allows the creation of a template for time series data streams using the Load JSON functionality.
Note: this pr doesn't make these fields configurable through the UI - this should be addressed separately.

The docs for new properties are here:

• https://www.elastic.co/guide/en/elasticsearch/reference/master/tsds.html#time-series-dimension
• https://www.elastic.co/guide/en/elasticsearch/reference/master/tsds.html#time-series-metric

You can test using this example template (try to create it through the UI and Load JSON for mappings): https://github.com/csoulios/downsampling-demo/blob/1e66a13bccc7d70aae7763bcc9c4499ec8b3fd02/downsample-ilm.es#L26-L169

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[Dosant]

@elasticmachine merge upstream

[yuliacech]

Hey @Dosant, thank you so much for adding the time series params!
I've been testing locally and I'm not sure that for time_series_metric this is the correct schema

schema: t.union([
      t.literal('gauge'),
      t.literal('counter'),
      t.literal('histogram'),
      t.literal('summary'),
      t.null,
    ]),

When I used histogram, the template creation failed with the following error: Failed to parse mapping: Unknown value [histogram] for field [time_series_metric] - accepted values are [gauge, counter]

[Dosant]

@yuliacech, thanks for catching this. they were removed: elastic/elasticsearch#89937
I'll update

[yuliacech]

Thanks for updating, @Dosant!

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 57cb0fa

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
indexManagement	522.8KB	523.0KB	+243.0B

History

• 💚 Build #71202 succeeded 5d20577
• 💛 Build #70435 was flaky a4efd9d

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