GlStackedColumnChart: Fix tooltip item order for tiled presentation

What does this MR do?

Fixes the tooltip item order in GlStackedColumnChart to account for the tiled presentation mode. Previously, tooltip items were always displayed in inverted order to match stacked columns from top to bottom, but this didn't make sense for tiled presentation where columns are displayed side-by-side. (For more context, see gitlab-org/gitlab!213207 (comment 2897838188)).

Screenshots or screen recordings

Before After
Screenshot 2025-11-24 at 1.01.05 PM.png Screenshot 2025-11-24 at 1.00.50 PM.png

With Multiple Stacks

Screenshot 2025-12-01 at 1.45.16 PM.png

Integrations

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”.
    • For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
  • Relevant label(s) are applied to the MR.
  • The MR is added to a milestone.
  • Added the ~"component:*" label(s) if applicable.
  • A changeset is added when this MR will do a patch, minor, or major update. More information can be found in doc/publishing-packages.md.

Components

  • GitLab UI's contributing guidelines.
  • If the MR changes a component's API, integration MR(s) have been opened (see integrations above).

Documentation

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Rudy Crespo

Merge request reports

Loading