[Lens] Add support for curved, linear and stepped lines

[nickofthyme]

Summary

Adds support for straight, smooth (curved) and step (after) curves on line and area charts in Lens.

closes #154410

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[nickofthyme]

@markov00 Can you review the naming and descriptions? I don't think descriptions are absolutely necessary but would be nice to have.

[markov00]

I would also suggest renaming the Curve type label to something else.
I feel that Interpolation or Line interpolation or Interpolation mode looks more specific and precise (you can't say that you are using a straight curve, but you have or a straight line or a curved line, IMHO and in my broken English knowledge)
I know that interpolation is not a daily used word by everyone, but this is anyway a technical software for technical people, and the use of technical words shouldn't be banned

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[stratoula]

@nickofthyme this works great and LGTM from me if @markov00 is ok. Do you want to also add the transition from TSVB to this PR?

When the users select Steps yes

and go to Lens we would like the Lens chart to have this curve.

It must be as simple as adding curveType: 'CURVE_STEP_AFTER', here

https://github.com/elastic/kibana/blob/main/src/plugins/vis_types/timeseries/public/convert_to_lens/lib/configurations/xy/configuration.ts#L21

when steps equals 1 in the TSVB series.

[stratoula]

This works great, I checked the transition from TSVB and also migrating 8.8 SOs. Everything LGTM! The FTs failing are also failing in main so I hope that they are going to skip it soon (I reported this to the team)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: dca9df9

Failed CI Steps

• FTR Configs #3

Test Failures

• [job] [logs] FTR Configs #3 / InfraOps App Metrics UI Metrics Explorer Saved Views should update the current saved view and load it

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
lens	885	886	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
expressionXY	163	165	+2
visualizations	779	780	+1
total			+3

Async chunks

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

id	before	after	diff
lens	1.2MB	1.2MB	+901.0B
visTypeTimeseries	507.7KB	507.9KB	+156.0B
total			+1.0KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
expressionXY	38.1KB	38.1KB	+47.0B
visualizations	56.5KB	56.6KB	+95.0B
total			+142.0B

Unknown metric groups

API count

id	before	after	diff
expressionXY	173	175	+2
visualizations	809	810	+1
total			+3

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
securitySolution	414	418	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
securitySolution	498	502	+4
total			+6

History

• 💔 Build #133651 failed a803784
• 💔 Build #133629 failed 867b9a4
• 💔 Build #133580 failed 12a1d6b
• 💔 Build #133573 failed 613bb64
• 💔 Build #133423 failed 02e18b4

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