[FEATURE] add tabs layout for dashboards

[jgbernalp]

Description

This PR adds support for tab layouts to dashboards, the current grid layout is left unchanged and the tabs support is additive. Tabs internally use the same grid system.

Part 2 of: perses/perses#4067
needs:

• [FEATURE] add tabs layout spec#24

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.

[sradco]

Hi @jgbernalp, any update on this?

[Nexucis]

I think Gabriel is off for a couple of days @sradco.

In the meantime, @Gladorme and / or @shahrokni can you review the PR please ?

[jgbernalp]

@sradco @Nexucis I marked it as draft as this needs a bit rework to define if the tabs are part of a group or not.

[sradco]

@sradco @Nexucis I marked it as draft as this needs a bit rework to define if the tabs are part of a group or not.

@jgbernalp Thanks for the update.
I think the question you're working through ("are tabs part of a group or not") aligns with what I asked on perses/perses#4068 - I think we want tabs as a top-level layout concept rather than nested inside a collapsible group. The tab bar itself would replace the group header, with each tab page still supporting collapsible grid sections internally.

Happy to help clarify the requirements or test once you have a direction. No rush.

[sradco]

Hi, Any update on this?