[ENHANCEMENT] TimeSeriesChart: add query name support for query settings

[Gladorme]

Description

Depends on: perses/shared#69

Add support for query name in query settings + deprecating queryIndex.

Migration guide:

• Via the UI:
  Go the dashboard, edit timeserieschart panel, go to query settings, update any value and save (it will migrate all query settings of the panel to queryName)

• Manually:
  Replace queryIndex by queryName.
  Replace number by string Query #<index + 1> or use helper defaultQueryName.
  Example: queryIndex: 0 become queryName: 'Query #1'.

Screenshots

Queries:

Query settings:

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.

[Nexucis]

that's a massive breaking change. This will break every dashboard created without dashboard as code or by migrating from Grafana.

[Gladorme]

Yeah, I will check if I can keep old data model

[Gladorme]

Ok, I remember why I did this change. We can't keep index, because it will cause issue when re-ordering queries with query settings. I will rename queryName to queryIndex, but result will be the same => they will need to update queryIndex.

[jgbernalp]

not sure why we are dropping the queryIndex, the index could be 0 and the name could be whatever. If name is a new field for better UX, queryIndex can be kept as it is.

[Gladorme]

@jgbernalp Yes, queryIndex is not more dropped, but set as optional

[jgbernalp]

I wonder why it should be optional. Using the name to index might not be a good strategy, IIUC the index defines the order (functional) and the name is for display (cosmetic).

[Gladorme]

Now that query can have name, I thought it was a nice idea to be based on it. But the more I think about it, the more I think it's better to stick to index for now and keep name only for cosmetic purpose.

The only drawback for query settings is: if you remove a query, it will change querysettings selector display. But it's already the case today, so I guess it's okay.

I will rollback to use queryIndex for functional purpose

[Gladorme]

Should be good now @jgbernalp / @shahrokni.

Btw, I think there a bug with query settings (already existing), if there are more than 1 series retuned by the query, the color is not applied (other styles are applied) or it's working as intended? 🤔

[shahrokni]

Should be good now @jgbernalp / @shahrokni.

Btw, I think there a bug with query settings (already existing), if there are more than 1 series retuned by the query, the color is not applied (other styles are applied) or it's working as intended? 🤔

I will take a look.