Transformations: Allow Timeseries to table transformation to handle multiple time series

[codeincarnate]

What is this feature?

This PR extends the capabilities of the Timeseries to table transformation to support multiple time series, even if those time series are embedded within a single data series. That is, it will be able to use a time field in combination with number fields and labeled data to breakdown time series data into distinct table rows.

Additionally, this also handles the case in which multiple series are present. Currently it doesn't modify multiple series which is actually a departure in behavior from how this transform worked previously in which multiple series would be mapped to a single one (i.e. even with multiple series the series selector for the table wouldn't appear).

I'm currently planning on adding an option (and making it the default) in order to preserve this behavior. However, it feels like we should update this in the future as currently multiple data series in the table panel will show a series selector. The default behavior of this transformation breaks that underlying structure

Beyond that, it currently assumes that the first time field found is the one that should be used to determine the time series. This isn't necessarily correct, and it's quite possible multiple time series could be present in the incoming data (e.g. created times vs update times for records is a straightforward example). I'll be adding an option for that.

Why do we need this feature?

This significantly enhances the capabilities of the Timeseries to table transformation to handle multiple data scenarios. In particular it should allow for this transformation to work across time series datasources, as well as other data sources with time data (e.g. SQL, App Analytics, etc.). This will allow multiple time series datums to be displayed together in a straightforward manner.

Who is this feature for?

Users that have multiple time series frames being returned from a single datasource.

Which issue(s) does this PR fix?:

Fixes #76291

Please check that:

• It works as expected from a user's perspective.
• If this is a pre-GA feature, it is behind a feature toggle.
• The docs are updated, and if this is a notable improvement, it's added to our What's New doc.

[codeincarnate]

Have this mostly working at this point. Working on one bug in which merging off all series from multiple queries isn't working right. Think I know how to solve that one.

[codeincarnate]

Did some cleanups and fixes and also fixed the test as the overall output has changed. Taking this out of draft so feedback can be incorporated. As far as I know the main thing missing at this point is a migration for the transformation settings.

[codeincarnate]

I found the problem, the options for other frames were being copied but not the options for the frame being modified 😭. That being said this should be fixed now 😄

[mdvictor]

Tested out the changes and LGTM!

[codeincarnate]

Currently looking into the GenAI tests failures so I don't blow up something important there. Otherwise though I think this is mostly ready to go.

[torkelo]

@codeincarnate would have been good if @domasx2 had reviewed this it looks to be a breaking change For app11y app that uses this

[torkelo]

Ah, see we have #77415 already 👍

[torkelo]

@codeincarnate I could not find any new tests that cover the new behavior, only modified tests that show a very big change in behavior from before, so hard to understand what the goal was here.

[codeincarnate]

Definitely a miss on this on my part, there were some parts of the original behavior I misunderstood. Working with @domasx2 on this now.