[Metric chart] Odd responsive behavior when Primary Metric is set to TOP

[gvnmagni]

Our current logic for responsiveness is based on the panel size but with the introduction of new features this could create a slightly odd behavior when the primary values is positioned on top.

When the panel is vertically resized, the component snap to the next breakpoint, as expected. Unfortunately, this is unexpected in common web practices because normally, those text should get smaller only when the lower limit of the panel reaches them. A behavior similar to what happens when the Primary Value font size is set to FIT (as seen in the following gif)

Now, we would need to test a logic in between. @mariairiartef do you think it is possible to introduce a new logic when the Primary Value is set to top position?

I know this would need maintain two logics and we need to evaluate all this obviously, but it would be great to see how it works.

Specifically, the behavior that we would like to test would be identical to the FIT behavior but instead of free resize, to snap from breakpoint to breakpoint when the panel gets resized.

@markov00 please feel free to add any detail in case I missed something or I didn't explain that clearly enough

[mariairiartef]

The current logic (using only the panel size for breakpoints) does not take into account the actual content present. If optional elements like extra are missing, the text may shrink sooner than users expect, especially when the primary value is positioned on top. I think we need to consider the presence or absence of these optional elements when determining breakpoints.