fix: prevent useTooltipTrigger from setting tabIndex

[abeljohn]

Closes #8556

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

[snowystinger]

property added in 53d8ed2

wasn't able to think of any counter example, but added some tests

[devongovett]

why is the undefined needed here at all?

[abeljohn]

the focusableProps here include a tabIndex, which then gets passed into FocusableContext. for the component consuming that context via useFocusable, the props from context (interactionProps) take precedence over the tabIndex determined by excludeFromTabOrder/isDisabled

another potential fix is to have useFocusable's calculated tabIndex take precedence over the props coming from the context, but that may be a riskier change

[devongovett]

Ok. I'm actually unsure why useTooltipTrigger calls useFocusable at all, since it is meant to pass the trigger props down to an element that already calls that (e.g. button). But looks like it's been there for 5+ years 🤷