BUG: Clicking "Tabs" component inside an Overlay triggers Overlay Closure (Dismiss)

[nvavna]

Summary
There is a usability bug when using the Tabs Selection component inside a screen opened as an Overlay. When a user attempts to switch tabs (e.g., clicking "Tab 2"), the entire Overlay frequently closes (dismisses) instead of switching the tab.
It appears the application interprets the click on the Tab header as a "Click Outside / Backdrop Click," causing the modal to close.

Severity: High (Usability)
This makes the Tabs component effectively unusable inside Overlays, as users accidentally close the form/screen constantly while trying to navigate.

Steps to Reproduce

1. Set up a screen to open as an Overlay.
2. Add a Tabs component (or a Choice component styled as segments) at the top.
3. Open the Overlay in the published app.
4. Try to click on a different Tab header (e.g., switch from Tab 1 to Tab 2).

Current Behavior

• The Overlay closes immediately (as if the user clicked the "X" or the background).
• Specific Detail: There is an extremely small, "pixel-perfect" safe zone (likely right on the text center) where the click does register correctly. However, if the user clicks slightly off-center (but still visually on the tab button), the Overlay closes.

Expected Behavior
Clicking anywhere within the visual boundary of the Tab component should only switch the tab. It should never trigger the "Close Overlay" action. The "Hit Box" for the tabs needs to be prioritized over the Overlay backdrop listener.