Floating UI: Review, validate, and test alignment - defaults, optional values, fallbackPlacement, fallbackAxisSideDirection

[tay1orjones]

Through #17248 we uncovered a logical error with how autoAlign positioned the OverflowMenu when the initial placement didn't fit. Similar issues exist in the other components with alignment options and that support autoAlign.

We need to go through and meticulously look at every component and variant (like isTabTip) to:

1. Determine if it's only allowing the approved alignments per component/variant
2. Ensure that it chooses the proper fallback alignment(s) when the default(s) don't fit
3. Standardize the auto align stories for each of these components to something that is polished, the same between all of them, and will work with VRT
4. Add these stories to VRT

There are very specific docs on the types of alignment options available to every popover-based element and variant. The same exists for Menus.

Important

If there is any confusion on how these should behave, the fallback order preference, etc., consult a design lead and document the decision in the issue.

Tasks

Preview Give feedback

1. Discuss and review the following components autoAlign behavior with design in a meeting:
2. Popover no caret
3. Popover with caret
4. Popover isTabTip
5. Toggletip
6. Tooltip
7. DefinitionTooltip
8. Menu
9. OverflowMenu (should be complete via fix(overflowmenu): improve autoAlign fallback placements #17248 but let's double check)
10. MenuButton
11. ComboButton
12. ... and anything else using useFloating that doesn't span the full width of the trigger element