[FEATURE] Add hide query button

[OrReuben]

Description

Attached to perses/perses#3884
Matches grafana's hide query button.
The idea is to let the user the ability to hide/show queries on the query level, and to make it stored in the JSON definition. this is in order to support stuff like math queries or any kind of other query that references a query result.

Screenshots

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.
• E2E tests are stable and unlikely to be flaky.
  See e2e docs for more details. Common issues include:
  • Is the data inconsistent? You need to mock API requests.
  • Does the time change? You need to use consistent time values or mock time utilities.
  • Does it have loading states? You need to wait for loading to complete.

[Nexucis]

this is in order to support stuff like math queries or any kind of other query that references a query result.

Maybe others will know what you talk about, but on my side I don't get the point of doing that. Can you explain a bit further what will be the point to hide a query. For me it's like putting a comment some lines of code, you can do it, but it's not clean and you should do it.

[OrReuben]

@Nexucis so the main idea of this feature is support of Expression queries, you could find the issue here:
perses/perses#3469

the visibility toggle is a killer feature when working with those kind of plugins - users would create multiple queries, and using the math query combine results together or execute math operations, but they don't really care about seeing the results from the queries on the graph, they want to see only the result of the expression, thats why we need a visibility toggle, a way for the user to define which queries he wants to see and doesn't want to see.

the legend on the graph does it aswell, but the main difference is that the legend visibility is not kept in the definition itself, and also each query could have multiple series, making it redundant to select/unselect multiple series together.

see example usage from our implementation:

[Nexucis]

Ah yeah ok makes more sense explained like that, thanks.

I think it will be much simpler for the definition and query and the number of PRs / release to make, once we are extracting the datasource and dashboard definitions to another repo.